Re: Testimonials for potential graduation announcement?

2017-03-17 Thread Jim Jagielski 
Presently, I cannot comment on my 'at-work' usage, but would
be willing to do so with my asf hat on, if that would be useful.

> On Mar 14, 2017, at 4:23 PM, Myrle Krantz  wrote:
> 
> Hello Fineracters
> 
> We are currently starting the process of graduation from the incubator.
> For the announcement (whenever that may be), we'd like to include customer
> testimonials.  Would anyone here like to provide a customer testimonial?
> How have you used Fineract?  How has it contributed to your success? Has
> the Fineract community supported you well?
> 
> Thanks in advance,
> Myrle

[jira] [Issue Comment Deleted] (FINERACT-418) Penalties should be calculated until yesterday

2017-03-17 Thread Santosh Math (JIRA) 

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

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

(was: [~lionel.raymundi], Send the pull request. )

> Penalties should be calculated until yesterday
> --
>
> Key: FINERACT-418
> URL: https://issues.apache.org/jira/browse/FINERACT-418
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>  Labels: p2
> Attachments: tests_with_modified_penalties_calculation_process.odt, 
> tests_with_monthly_penalties.ods
>
>
> If the Apply Penalties to Overdued loans job is run on the N day, and 
> considering that system properties Grace on Penalty posting = 0 and 
> penalty-wait-period = 0, then charges should be generated until N-1 (the day 
> before N). But I see only charges generated until N-2 (Two days before).
> We have noticed that penalty charges are being generated one day late for 
> some cases. For example: 
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged daily.
> .- System configuration has Grace on Penalty posting = 0 and 
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that 
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
> .- I would also expect to see the charge generated with due as of date 05 and 
> 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-418) Penalties should be calculated until yesterday

2017-03-17 Thread Santosh Math (JIRA) 

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

Santosh Math commented on FINERACT-418:
---

[~lionel.raymundi], Send the pull request. 

> Penalties should be calculated until yesterday
> --
>
> Key: FINERACT-418
> URL: https://issues.apache.org/jira/browse/FINERACT-418
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>  Labels: p2
> Attachments: tests_with_modified_penalties_calculation_process.odt, 
> tests_with_monthly_penalties.ods
>
>
> If the Apply Penalties to Overdued loans job is run on the N day, and 
> considering that system properties Grace on Penalty posting = 0 and 
> penalty-wait-period = 0, then charges should be generated until N-1 (the day 
> before N). But I see only charges generated until N-2 (Two days before).
> We have noticed that penalty charges are being generated one day late for 
> some cases. For example: 
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged daily.
> .- System configuration has Grace on Penalty posting = 0 and 
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that 
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
> .- I would also expect to see the charge generated with due as of date 05 and 
> 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-418) Penalties should be calculated until yesterday

2017-03-17 Thread Lionel Raymundi (JIRA) 

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

Lionel Raymundi commented on FINERACT-418:
--

[~santoshmath] I see what you mean, but it is not the issue I've been working 
on. This is the typical behavior of fineract, as it creates a penalty charge 
for each installment overdue and for each period defined in the charge 
configuration. Of course, if you see the installment plan, you will find the 
sum of all the charges that apply to the same installment.
The only modification I made, is that the penalty charge creation is not 
delayed one day. If that is ok, I will create the pull request for you to check

> Penalties should be calculated until yesterday
> --
>
> Key: FINERACT-418
> URL: https://issues.apache.org/jira/browse/FINERACT-418
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>  Labels: p2
> Attachments: tests_with_modified_penalties_calculation_process.odt, 
> tests_with_monthly_penalties.ods
>
>
> If the Apply Penalties to Overdued loans job is run on the N day, and 
> considering that system properties Grace on Penalty posting = 0 and 
> penalty-wait-period = 0, then charges should be generated until N-1 (the day 
> before N). But I see only charges generated until N-2 (Two days before).
> We have noticed that penalty charges are being generated one day late for 
> some cases. For example: 
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged daily.
> .- System configuration has Grace on Penalty posting = 0 and 
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that 
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
> .- I would also expect to see the charge generated with due as of date 05 and 
> 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-321) Manual Journal entries should not allowed to reverse after accounting closure is done for that branch

2017-03-17 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on FINERACT-321:
-

GitHub user nazeer1100126 opened a pull request:

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

FINERACT-321 - Manual Journal entries should not allowed to reverse after 
accounting closure is done for that branch.



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

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

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

https://github.com/apache/incubator-fineract/pull/318.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 #318


commit 5f74453606db080ae96fafbd58b0a5df96b5362c
Author: nazeer1100126 
Date:   2017-03-17T12:19:05Z

FINERACT-321 - Manual Journal entries should not allowed to reverse after 
accounting closure is done for that branch




> Manual Journal entries should not allowed to reverse after accounting closure 
> is done for that branch
> -
>
> Key: FINERACT-321
> URL: https://issues.apache.org/jira/browse/FINERACT-321
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Accounting
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p2
>
> Reported by Subramanya  at https://mifosforge.jira.com/browse/MIFOSX-2519
> Original Description:
> 1. Create 2 Chart of accounts with Asset1 and Asset 2.
> 2. Click on accounting -> Add Journal entries -> Add one debit and Credit 
> entries with above entities on 31 January 2016.
> 3. Click on Accounting and Click on Closing entries and close the accounting 
> entries for the organization on 01 February 2016.
> 4. Navigate back to the journal entries created and click on reverse entries. 
> It is allowing to reverse.
> > It should not allowed to reverse the entries once Accounting entry is 
> > closed for the branch



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (FINERACT-330) No error message is getting displayed in productive collection sheet if meeting is not attached to center/group

2017-03-17 Thread Shaik Nazeer Hussain (JIRA) 

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

Shaik Nazeer Hussain reassigned FINERACT-330:
-

Assignee: Santosh Math  (was: Shaik Nazeer Hussain)

> No error message is  getting displayed in productive collection sheet if 
> meeting is not attached  to center/group
> -
>
> Key: FINERACT-330
> URL: https://issues.apache.org/jira/browse/FINERACT-330
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Client, Groups
>Reporter: Santosh Math
>Assignee: Santosh Math
>Priority: Minor
>  Labels: p2
> Fix For: 0.7.0-incubating
>
> Attachments: 1.png
>
>
> Steps to reproduce:
> 1. Create a center under Head Office and activate it on 01 Jan 2013.Attach 
> staff. Don't attach meeting.
> 2. Create a group under this center and activate it on 01 Jan 2013.
> 3. Create a client in this group with activation date 01 Jan 2013
> 4. Approve and Disburse JLG Loan(Frequeny weekly repayment) 02 Jan 2015.
> 5. Go to collection sheet. and select:
> Branch Office: Head Office
> Meeting Calender: 09 Jan 2015
> Staff: *provide same staff name of the  center
> 6. Click on "Productive Collection Sheet".
> In Productive Collection Sheet page, there is no error message is displayed 
> related to meeting not attached.
> Expected Result: the error message should be displayed as "Collection can not 
> be generated without meeting attached to center"
>   



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (FINERACT-330) No error message is getting displayed in productive collection sheet if meeting is not attached to center/group

2017-03-17 Thread Shaik Nazeer Hussain (JIRA) 

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

Shaik Nazeer Hussain resolved FINERACT-330.
---
   Resolution: Fixed
Fix Version/s: 0.7.0-incubating

> No error message is  getting displayed in productive collection sheet if 
> meeting is not attached  to center/group
> -
>
> Key: FINERACT-330
> URL: https://issues.apache.org/jira/browse/FINERACT-330
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Client, Groups
>Reporter: Santosh Math
>Assignee: Shaik Nazeer Hussain
>Priority: Minor
>  Labels: p2
> Fix For: 0.7.0-incubating
>
> Attachments: 1.png
>
>
> Steps to reproduce:
> 1. Create a center under Head Office and activate it on 01 Jan 2013.Attach 
> staff. Don't attach meeting.
> 2. Create a group under this center and activate it on 01 Jan 2013.
> 3. Create a client in this group with activation date 01 Jan 2013
> 4. Approve and Disburse JLG Loan(Frequeny weekly repayment) 02 Jan 2015.
> 5. Go to collection sheet. and select:
> Branch Office: Head Office
> Meeting Calender: 09 Jan 2015
> Staff: *provide same staff name of the  center
> 6. Click on "Productive Collection Sheet".
> In Productive Collection Sheet page, there is no error message is displayed 
> related to meeting not attached.
> Expected Result: the error message should be displayed as "Collection can not 
> be generated without meeting attached to center"
>   



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (FINERACT-330) No error message is getting displayed in productive collection sheet if meeting is not attached to center/group

2017-03-17 Thread Shaik Nazeer Hussain (JIRA) 

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

Shaik Nazeer Hussain reassigned FINERACT-330:
-

Assignee: Shaik Nazeer Hussain  (was: Markus Geiss)

> No error message is  getting displayed in productive collection sheet if 
> meeting is not attached  to center/group
> -
>
> Key: FINERACT-330
> URL: https://issues.apache.org/jira/browse/FINERACT-330
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Client, Groups
>Reporter: Santosh Math
>Assignee: Shaik Nazeer Hussain
>Priority: Minor
>  Labels: p2
> Attachments: 1.png
>
>
> Steps to reproduce:
> 1. Create a center under Head Office and activate it on 01 Jan 2013.Attach 
> staff. Don't attach meeting.
> 2. Create a group under this center and activate it on 01 Jan 2013.
> 3. Create a client in this group with activation date 01 Jan 2013
> 4. Approve and Disburse JLG Loan(Frequeny weekly repayment) 02 Jan 2015.
> 5. Go to collection sheet. and select:
> Branch Office: Head Office
> Meeting Calender: 09 Jan 2015
> Staff: *provide same staff name of the  center
> 6. Click on "Productive Collection Sheet".
> In Productive Collection Sheet page, there is no error message is displayed 
> related to meeting not attached.
> Expected Result: the error message should be displayed as "Collection can not 
> be generated without meeting attached to center"
>   



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-418) Penalties should be calculated until yesterday

2017-03-17 Thread Santosh Math (JIRA) 

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

Santosh Math commented on FINERACT-418:
---

[~lionel.raymundi], If previous penalties are not paid ,let's say, 01 Feb and 
01 March are not paid then on 01 April, it should display summation of both 
charges rather than individual charges(in my opinion).

> Penalties should be calculated until yesterday
> --
>
> Key: FINERACT-418
> URL: https://issues.apache.org/jira/browse/FINERACT-418
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>  Labels: p2
> Attachments: tests_with_modified_penalties_calculation_process.odt, 
> tests_with_monthly_penalties.ods
>
>
> If the Apply Penalties to Overdued loans job is run on the N day, and 
> considering that system properties Grace on Penalty posting = 0 and 
> penalty-wait-period = 0, then charges should be generated until N-1 (the day 
> before N). But I see only charges generated until N-2 (Two days before).
> We have noticed that penalty charges are being generated one day late for 
> some cases. For example: 
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged daily.
> .- System configuration has Grace on Penalty posting = 0 and 
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that 
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
> .- I would also expect to see the charge generated with due as of date 05 and 
> 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (FINERACT-243) Constitution Type Required Field

2017-03-17 Thread Shaik Nazeer Hussain (JIRA) 

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

Shaik Nazeer Hussain resolved FINERACT-243.
---
   Resolution: Fixed
 Assignee: Santosh Math  (was: Shaik Nazeer Hussain)
Fix Version/s: 0.7.0-incubating

With PR https://github.com/apache/incubator-fineract/pull/313, this issue will 
be fixed. 

> Constitution Type Required Field
> 
>
> Key: FINERACT-243
> URL: https://issues.apache.org/jira/browse/FINERACT-243
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Dayna Harp
>Assignee: Santosh Math
>Priority: Critical
>  Labels: p2
> Fix For: 0.7.0-incubating
>
>
> when creating a client with Legal Form "Entity", Constitution is a required 
> field.  This does not need to be required.  It is an optional field for those 
> financial institutions serving groups that have a constitution.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (FINERACT-243) Constitution Type Required Field

2017-03-17 Thread Shaik Nazeer Hussain (JIRA) 

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

Shaik Nazeer Hussain reassigned FINERACT-243:
-

Assignee: Shaik Nazeer Hussain  (was: Markus Geiss)

> Constitution Type Required Field
> 
>
> Key: FINERACT-243
> URL: https://issues.apache.org/jira/browse/FINERACT-243
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Dayna Harp
>Assignee: Shaik Nazeer Hussain
>Priority: Critical
>  Labels: p2
>
> when creating a client with Legal Form "Entity", Constitution is a required 
> field.  This does not need to be required.  It is an optional field for those 
> financial institutions serving groups that have a constitution.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)