[jira] [Commented] (FINERACT-633) New Penalty Charge not appearing in Product dropdown list
[ https://issues.apache.org/jira/browse/FINERACT-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712398#comment-16712398 ] Sifiso Mtetwa commented on FINERACT-633: Thanks Ed, We had put it on hold but can push it for completion now. However some assistance from Sampath or Shruthi or any willing community developer who is privy to charges maybe necessary. Kind regards, Sifiso > New Penalty Charge not appearing in Product dropdown list > - > > Key: FINERACT-633 > URL: https://issues.apache.org/jira/browse/FINERACT-633 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Loan >Affects Versions: 1.1.0 > Environment: v18.03.01 >Reporter: Sifiso Mtetwa >Priority: Minor > Labels: easyfix, gsoc, p1 > Fix For: 1.4.0 > > > We have been developing a new feature for penalties overdue on maturity > [https://mifosforge.jira.com/browse/MIFOSX-2848?filter=-2] We have an issue > where after you create the penalty in the charges area with a new charge time > type of overdue on maturity and submit it, it does not appear in loan > products penalties dropdown box for selection. Wanted to find out which class > fetches the penalties that are fetched to appear in this list yet in table > m_charges it appears fine. We have added some code in the UI to fetch the > required variables but it still does not appear. We can’t proceed beyond this > point. Please advise -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-440) Include runningBalance, appUser in m_share_account_transactions table.
[ https://issues.apache.org/jira/browse/FINERACT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712377#comment-16712377 ] Ippez Roberts commented on FINERACT-440: Hi Ed, Yes these parameters are used for generating reports, like Share statements for example. > Include runningBalance, appUser in m_share_account_transactions table. > -- > > Key: FINERACT-440 > URL: https://issues.apache.org/jira/browse/FINERACT-440 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gci, gsoc, p2 > Fix For: 1.4.0 > > > Include the two parameters runningBalance, appUser in > m_share_account_transactions to be used to generate Share Transaction > Statement. Currently its not posible to generate standard statement since > runningBalance is missing and kind of hard to determine it from current Share > Transaction table -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712368#comment-16712368 ] Shruthi M R commented on FINERACT-276: --- [~mgeiss] have you started working on this? If not I would like to work on this. So kindly let me know. > 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 >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > 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 (v7.6.3#76005)
[jira] [Commented] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712367#comment-16712367 ] Shruthi M R commented on FINERACT-276: --- [~edcable] sure, will start working on this. > 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 >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > 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 (v7.6.3#76005)
[jira] [Commented] (FINERACT-363) Penalty to be attached/updated to a loan account which was created when a loan product had no penalty/penalty with different amount
[ https://issues.apache.org/jira/browse/FINERACT-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712362#comment-16712362 ] Shruthi M R commented on FINERACT-363: --- [~edcable] I haven't started working on this yet. > Penalty to be attached/updated to a loan account which was created when a > loan product had no penalty/penalty with different amount > > > Key: FINERACT-363 > URL: https://issues.apache.org/jira/browse/FINERACT-363 > Project: Apache Fineract > Issue Type: Bug > Components: Charges >Reporter: Mexina Daniel >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > 1. Create a loan product without overdue charges (penalty) in Admin -> > Product -> Loan Product -> Create Loan Product > 2. Apply a loan account of that loan product to a client at Clients -> View > Client -> New Loan > 3. Approve a loan, disburse and make few repayments > 4. Then create a charge which is overdue (is penalty) in Admin -> Products -> > Charges -> Create Charge > 5. Go to that loan product and attach an overdue charge > What happens: > The applied penalty is also attached to that loan which was created before > this update > Expected: > The loan account should not be updated if it was created before the change, > the penalty should be applied to loan accounts that will be applied after > update of loan product. > 6. Update a penalty and change it's amount > What happens: > All loan accounts that the penalty is applied, the amount of the penalty will > also change. > Expected: > The amount of the penalty should not change to the loan accounts that were > attached before the update of the penalty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-478) Savings overdraft fee with charge time type 'overdraft fee' and charge calculation '%amount' is not working
[ https://issues.apache.org/jira/browse/FINERACT-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712360#comment-16712360 ] Shruthi M R commented on FINERACT-478: --- [~edcable] Fineract-478 and Fineract-641 are not related. > Savings overdraft fee with charge time type 'overdraft fee' and charge > calculation '%amount' is not working > --- > > Key: FINERACT-478 > URL: https://issues.apache.org/jira/browse/FINERACT-478 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Savings >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > > 1. Go to charges and select charge applied to 'Savings and deposits' > 2. Fill other required inputs with > Charge Time type: overdraft fee > Charge calculation : % amount. > Amount : 1 > > After submission , it is throwing error: > > "validation.msg.charges.charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivity" > Expected: > 1.This feature of overdraft fee with charge calculation as % amount need to > be implemented. > 2. Until the feature is implemented, the following proper error message > should be thrown in stead of above mentioned: > ""validation.msg: > charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivityand > yet to be implemented for overdraft fee" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-574) Issues related to share Account Creation
[ https://issues.apache.org/jira/browse/FINERACT-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712355#comment-16712355 ] Shruthi M R commented on FINERACT-574: --- [~edcable] on top [~Nenge1] PR (which I merged) I have provided fix to the other part of the issue '[https://github.com/apache/fineract/pull/498'] . Once this is reviewed and merged I will resolve the issue. > Issues related to share Account Creation > > > Key: FINERACT-574 > URL: https://issues.apache.org/jira/browse/FINERACT-574 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: gci, gsoc, p1 > Fix For: 1.3.0 > > Attachments: Screenshot from 2017-12-12 21-05-47.png > > > 1. Create Share Product with Accounting Enabled > 2. Create a share charge with type 'Share Purchase' ,'Flat' amount $2. > 3. Create and activate savings account for client which is needed to link > with share account > 4. Create a share Account application for current date using above product > and charge and number of shares issued as 10 , each share price as $0.5. > > Once you 'Submit' the share application journal entries are created > > (including charge) even though share account is not yet approved/activated. > >Approve the share account and again duplicate jounal entries are created. > >If share account application is attached with 'Share Activation Fee' , upon > >submission of share account application, if we check 'Transaction Overview' > >tab, it shows 'Activation Fee' is received even though share account is not > >activated. Same is updated in the database > >table,"m_share_account_charge_paid_by". But under the 'Charges' tab, it > >shows Outstanding(which is correct). > The all scenarios can be tested here by modifying application and using the > charges > 'Share Purchase Fee' or 'Share Activation Fee' > https://staging.openmf.org/#/viewshareaccount/5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-638) Creation of API's for Web App and Self Service Admin Portal
[ https://issues.apache.org/jira/browse/FINERACT-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712351#comment-16712351 ] Shruthi M R commented on FINERACT-638: --- [~edcable] we are in the designing phase > Creation of API's for Web App and Self Service Admin Portal > --- > > Key: FINERACT-638 > URL: https://issues.apache.org/jira/browse/FINERACT-638 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization, System, User Management >Reporter: Abhay Chawla >Assignee: Shruthi M R >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > > List of API's that will be required are as follows- > App Configuration for the new web app, based on the Tenant so that they can > be accessed on the login page itself before authentication: > 1) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format > 2) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name > 3) Support for saving and retrieving Default theme and font to be used within > the application > 4) Support for saving and retrieving contact information including website, > email, contact no (multiple if required) > App Configuration for the self-service mobile app and online banking app, > based on Tenant so that they can be accessed on the login page itself before > authentication: > 5) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format (common) > 6) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name (common and will be used as > required by whichever application) > 7) Support for saving and retrieving Default theme and font to be used within > the application (separate for mobile and online banking app) > 8) Support for saving and retrieving contact information including website, > email, contact no (common, multiple if required) > Self Service User Management and Creation > 1) Support for viewing current and potential self-service users. > 2) Support for activating and deactivating self-service users (single and > bulk). > 3) Support for creating new self-service users. > 4) Support for viewing, editing and changing the password of a self-service > user. > Refer to Issues: > https://github.com/openMF/web-app/issues/33 > https://github.com/openMF/web-app/issues/34 > https://github.com/openMF/web-app/issues/35 > https://github.com/openMF/web-app/issues/36 > Self Service JIRA Link: > https://mifosforge.jira.com/wiki/spaces/MIFOSX/pages/102629583/Customer+Self+Service -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-12) For Overdue/Due Fee/Int,Principal strategy with variable installment, late repayment is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712333#comment-16712333 ] Santosh Math commented on FINERACT-12: -- [~edcable], Yes, this issue still exists. > For Overdue/Due Fee/Int,Principal strategy with variable installment, late > repayment is not working as expected > --- > > Key: FINERACT-12 > URL: https://issues.apache.org/jira/browse/FINERACT-12 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p1 > Fix For: 1.4.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2401 > 1. Create loan product with following datasets, > Terms > Terms vary based on loan cycle : false > Principal: 10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate: 1 ( Min: , Max) Per month > Minimum days between disbursal and first repayment date > Settings > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Arrears Tolerance > Repayment Strategy Overdue/Due Fee/Int,Principal > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amount No > Variable Installments (Min:0 , Max:365) > Interest Recalculation > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01 October 2015 > Is Arrears recognization based on original schedule No > 2. Create a client and submit new loan application on 01 October 2015. > 3. Click on More -> Edit repayment schedule in which delete repayment for 01 > November 2015 and click on validate and submit button. > 4. Approve and disburse loan on 01 October 2015. > 5. Make repayment on 15 December 2015. > > In Overdue/Due Fee/Int,Principal repayment strategy one entry on 15 > > December 2015 should get created, which is not getting getting created. > > Interest should get calculated upto 14 December 2015. (Disbursement date 01 > > October 2015 and first repayment is doing on 15 December 2015). > Attachments: https://mifosforge.jira.com/browse/MIFOSX-2401 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-13) Multi-tranche Loan repayment on 2nd tranche incorrect
[ https://issues.apache.org/jira/browse/FINERACT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712335#comment-16712335 ] Santosh Math commented on FINERACT-13: -- [~edcable], Yes, This issue still exists and never worked on. > Multi-tranche Loan repayment on 2nd tranche incorrect > - > > Key: FINERACT-13 > URL: https://issues.apache.org/jira/browse/FINERACT-13 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p1 > Fix For: 1.3.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2398 - See for attachments > 1. Create a loan product with following data sets, > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max) Per month > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyPenalties, Fees, Interest, Principal order > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Sep-15 > Enable Multiple DisbursalsTRUE > Maximum Tranche count 2 > Maximum allowed outstanding balance 1 > 2. Create specified due date charge 1% of amount and attache to the above > loan product, > 3. Submit new loan application for a client on 01 September 2015 with first > tranche of 5000 on same date and second tranche on 01 November 2015 and > amount 5000. Add specified due date charge date as 15 September 2015. > 4. Make repayment on 01 October 2015 in which charge applied on 15 September > 2015 got collected and amount as 50 (1% of disbursed amount). > 5. Disburse 2nd tranche as 5000 on 01 November 2015. > > In the repayment schedule 50 is displaying as balance in 01 October 2015 > > repayment. > > Application Should not allowed to modify or apply charge for the repayment > > which is already paid -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-348) Issues when doing a "Close-As-Rescheduled" on a loan
[ https://issues.apache.org/jira/browse/FINERACT-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712303#comment-16712303 ] Santosh Math commented on FINERACT-348: --- [~edcable] , In my opinion, it was partially implemented long back based on specific requirement by a client. I need to know any one from the Community need this feature. > 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: gsoc, p1 > Fix For: 1.4.0 > > > 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 (v7.6.3#76005)
[jira] [Updated] (FINERACT-466) For the loans without Interest Recalculation, Prepay Loan is collecting all installment Fees in stead of collecting installment fees until the prepay date
[ https://issues.apache.org/jira/browse/FINERACT-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-466: -- Issue Type: Bug (was: Improvement) > For the loans without Interest Recalculation, Prepay Loan is collecting all > installment Fees in stead of collecting installment fees until the prepay date > -- > > Key: FINERACT-466 > URL: https://issues.apache.org/jira/browse/FINERACT-466 > Project: Apache Fineract > Issue Type: Bug > Components: Charges, Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > > 1. Create a loan product without Interest recalculation,monthly repayment, > Equal Installments, Declining balance and 12 repayments with installment fee > 100((flat, monthly) attached. > 2. Disburse the loan on 01 January 2017. > 3 Prepay the loan on 15 February 2017. > > Expected Result: The installment fee should be collected: 100 > >Actual Result: The installment fee getting collected: 1200(all installment > >fees) > P.S: This issue doesn't exist with loans having interest recalculation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-478) Savings overdraft fee with charge time type 'overdraft fee' and charge calculation '%amount' is not working
[ https://issues.apache.org/jira/browse/FINERACT-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712300#comment-16712300 ] Santosh Math commented on FINERACT-478: --- [~edcable], Are you trying to mention another ticket in stead of 478 in your comment? > Savings overdraft fee with charge time type 'overdraft fee' and charge > calculation '%amount' is not working > --- > > Key: FINERACT-478 > URL: https://issues.apache.org/jira/browse/FINERACT-478 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Savings >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > > 1. Go to charges and select charge applied to 'Savings and deposits' > 2. Fill other required inputs with > Charge Time type: overdraft fee > Charge calculation : % amount. > Amount : 1 > > After submission , it is throwing error: > > "validation.msg.charges.charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivity" > Expected: > 1.This feature of overdraft fee with charge calculation as % amount need to > be implemented. > 2. Until the feature is implemented, the following proper error message > should be thrown in stead of above mentioned: > ""validation.msg: > charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivityand > yet to be implemented for overdraft fee" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-381) Repayment schedule mismatch before approval and after approval when two consecutive holidays comes on repayment
[ https://issues.apache.org/jira/browse/FINERACT-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-381: -- Fix Version/s: (was: 1.3.0) > Repayment schedule mismatch before approval and after approval when two > consecutive holidays comes on repayment > --- > > Key: FINERACT-381 > URL: https://issues.apache.org/jira/browse/FINERACT-381 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Avinash Dalvi >Assignee: Markus Geiss >Priority: Critical > Labels: p1 > Attachments: image001.jpg, image002.jpg > > > Have configured a loan product with declining balance, recalculate > interest, and frequency for recalculate outstanding principal as ?same as > repayment period?. System is configured to have payments due on non working > days to be moved to next working day. Found that the date when the > principal is recalculated is not the same date as expected EMI / repayment > date in case the repayment date is a holiday. > Loan configuration screen shot: > The repayment schedule comes like below: The interest computed of 3,682 is > on the principal of 200,000 rather than 134,894, as the outstanding > principal calculation was done based on principal on 12th Feb and not 13th > Feb which is the date of EMI payment. Please refer to the screen shot > below. Same happens for interest of 2,661 which is based on 134,894 rather > than 69,262. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (FINERACT-381) Repayment schedule mismatch before approval and after approval when two consecutive holidays comes on repayment
[ https://issues.apache.org/jira/browse/FINERACT-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math reopened FINERACT-381: --- > Repayment schedule mismatch before approval and after approval when two > consecutive holidays comes on repayment > --- > > Key: FINERACT-381 > URL: https://issues.apache.org/jira/browse/FINERACT-381 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Avinash Dalvi >Assignee: Markus Geiss >Priority: Critical > Labels: p1 > Attachments: image001.jpg, image002.jpg > > > Have configured a loan product with declining balance, recalculate > interest, and frequency for recalculate outstanding principal as ?same as > repayment period?. System is configured to have payments due on non working > days to be moved to next working day. Found that the date when the > principal is recalculated is not the same date as expected EMI / repayment > date in case the repayment date is a holiday. > Loan configuration screen shot: > The repayment schedule comes like below: The interest computed of 3,682 is > on the principal of 200,000 rather than 134,894, as the outstanding > principal calculation was done based on principal on 12th Feb and not 13th > Feb which is the date of EMI payment. Please refer to the screen shot > below. Same happens for interest of 2,661 which is based on 134,894 rather > than 69,262. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-381) Repayment schedule mismatch before approval and after approval when two consecutive holidays comes on repayment
[ https://issues.apache.org/jira/browse/FINERACT-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-381. - Resolution: Cannot Reproduce > Repayment schedule mismatch before approval and after approval when two > consecutive holidays comes on repayment > --- > > Key: FINERACT-381 > URL: https://issues.apache.org/jira/browse/FINERACT-381 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Avinash Dalvi >Assignee: Markus Geiss >Priority: Critical > Labels: p1 > Attachments: image001.jpg, image002.jpg > > > Have configured a loan product with declining balance, recalculate > interest, and frequency for recalculate outstanding principal as ?same as > repayment period?. System is configured to have payments due on non working > days to be moved to next working day. Found that the date when the > principal is recalculated is not the same date as expected EMI / repayment > date in case the repayment date is a holiday. > Loan configuration screen shot: > The repayment schedule comes like below: The interest computed of 3,682 is > on the principal of 200,000 rather than 134,894, as the outstanding > principal calculation was done based on principal on 12th Feb and not 13th > Feb which is the date of EMI payment. Please refer to the screen shot > below. Same happens for interest of 2,661 which is based on 134,894 rather > than 69,262. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-494) Issue when selecting savings account on client creation page
[ https://issues.apache.org/jira/browse/FINERACT-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math closed FINERACT-494. - > Issue when selecting savings account on client creation page > > > Key: FINERACT-494 > URL: https://issues.apache.org/jira/browse/FINERACT-494 > Project: Apache Fineract > Issue Type: Bug > Components: Client, Savings >Reporter: Chanda Aparna >Assignee: Santosh Math >Priority: Major > Labels: p1 > Fix For: 1.1.0 > > Attachments: client page.jpg > > > When user checks open savings account on the client creation page, the > savings product dropdown is enabled. All the savings product irrespective of > Recurring or Saving deposits will be displayed in that. Once the saving > product(recurring product with ismandatory checked) is selected and submitted > the client page, the selected savings product which is recurring with > ismandatory flag true is saved as saving deposit(deposit_type_enum: 100) > instead of recurring deposit(deposit_type_enum: 300) in savings table > (m_savings_account) with the created client id, which is a bug. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-12) For Overdue/Due Fee/Int,Principal strategy with variable installment, late repayment is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-12: - Labels: V p1 (was: p1) > For Overdue/Due Fee/Int,Principal strategy with variable installment, late > repayment is not working as expected > --- > > Key: FINERACT-12 > URL: https://issues.apache.org/jira/browse/FINERACT-12 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p1 > Fix For: 1.4.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2401 > 1. Create loan product with following datasets, > Terms > Terms vary based on loan cycle : false > Principal: 10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate: 1 ( Min: , Max) Per month > Minimum days between disbursal and first repayment date > Settings > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Arrears Tolerance > Repayment Strategy Overdue/Due Fee/Int,Principal > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amount No > Variable Installments (Min:0 , Max:365) > Interest Recalculation > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01 October 2015 > Is Arrears recognization based on original schedule No > 2. Create a client and submit new loan application on 01 October 2015. > 3. Click on More -> Edit repayment schedule in which delete repayment for 01 > November 2015 and click on validate and submit button. > 4. Approve and disburse loan on 01 October 2015. > 5. Make repayment on 15 December 2015. > > In Overdue/Due Fee/Int,Principal repayment strategy one entry on 15 > > December 2015 should get created, which is not getting getting created. > > Interest should get calculated upto 14 December 2015. (Disbursement date 01 > > October 2015 and first repayment is doing on 15 December 2015). > Attachments: https://mifosforge.jira.com/browse/MIFOSX-2401 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-12) For Overdue/Due Fee/Int,Principal strategy with variable installment, late repayment is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712142#comment-16712142 ] Edward Cable commented on FINERACT-12: -- [~santoshmath] can you confirm that this issue is still present? > For Overdue/Due Fee/Int,Principal strategy with variable installment, late > repayment is not working as expected > --- > > Key: FINERACT-12 > URL: https://issues.apache.org/jira/browse/FINERACT-12 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p1 > Fix For: 1.4.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2401 > 1. Create loan product with following datasets, > Terms > Terms vary based on loan cycle : false > Principal: 10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate: 1 ( Min: , Max) Per month > Minimum days between disbursal and first repayment date > Settings > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Arrears Tolerance > Repayment Strategy Overdue/Due Fee/Int,Principal > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amount No > Variable Installments (Min:0 , Max:365) > Interest Recalculation > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01 October 2015 > Is Arrears recognization based on original schedule No > 2. Create a client and submit new loan application on 01 October 2015. > 3. Click on More -> Edit repayment schedule in which delete repayment for 01 > November 2015 and click on validate and submit button. > 4. Approve and disburse loan on 01 October 2015. > 5. Make repayment on 15 December 2015. > > In Overdue/Due Fee/Int,Principal repayment strategy one entry on 15 > > December 2015 should get created, which is not getting getting created. > > Interest should get calculated upto 14 December 2015. (Disbursement date 01 > > October 2015 and first repayment is doing on 15 December 2015). > Attachments: https://mifosforge.jira.com/browse/MIFOSX-2401 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-505) Loan Tranche Details should be captured in Bulk JLG loan application.
[ https://issues.apache.org/jira/browse/FINERACT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-505: -- Fix Version/s: (was: 1.4.0) Backlog > Loan Tranche Details should be captured in Bulk JLG loan application. > - > > Key: FINERACT-505 > URL: https://issues.apache.org/jira/browse/FINERACT-505 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > Fix For: Backlog > > > Presently, there is no fields to capture multi-tranche details in 'Bulk JLG > loan application' . Therefore, Bulk JLG loan application doesn't support > multi-tranche loan products. The current temperory fix is, the loan products > with multi-tranche aren't displaying in drop-down menu of 'Bulk JLG loan > application'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-26) Allow a Logo (for Organization) to be set, which will be displayed on the header
[ https://issues.apache.org/jira/browse/FINERACT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712136#comment-16712136 ] Edward Cable commented on FINERACT-26: -- [~abhaychawla] Can you please comment on this issue as to how the web app rewrite is addressing skinning/theming and adding custom logo? > Allow a Logo (for Organization) to be set, which will be displayed on the > header > > > Key: FINERACT-26 > URL: https://issues.apache.org/jira/browse/FINERACT-26 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p1 > Fix For: 1.3.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2511 > As a Implementation Specialist, I wish to setup a logo (for the organization) > which will be displayed before the Mifos logo > As a first step : there is no user interface needed for uploading the logo. > As a second step : we can provide user interface for logo-upload > Logo can be different for different tenants (in a multi-tenant setup). > Logo should be same size as Mifos X logo - to maintain aesthetics of the > header band. > Part 2 ] While we are at it, we should probably also allow themes to be > picked on on a per tenant basis -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-281) Periodic accrual on a particular day is not calculating as expected
[ https://issues.apache.org/jira/browse/FINERACT-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-281: -- Labels: Volunteer confirm p1 (was: confirm p1) > Periodic accrual on a particular day is not calculating as expected > --- > > Key: FINERACT-281 > URL: https://issues.apache.org/jira/browse/FINERACT-281 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, confirm, p1 > Fix For: 1.3.0 > > Attachments: Scr-339.png, Scr-340.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1487 > Original Description: > If Loan disbursed on 05 june 2014, first repayment falls on 19 june 2014 and > If periodic accrual on a particular day ie on 30 june 2014 is run then > accrued interest between 19 june 2014 to 30 june 2014 should be calculated > and displayed instead it is displaying accrued interest from 05 june 2014 to > 30 june 2014. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-12) For Overdue/Due Fee/Int,Principal strategy with variable installment, late repayment is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-12: - Fix Version/s: (was: 1.3.0) 1.4.0 > For Overdue/Due Fee/Int,Principal strategy with variable installment, late > repayment is not working as expected > --- > > Key: FINERACT-12 > URL: https://issues.apache.org/jira/browse/FINERACT-12 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p1 > Fix For: 1.4.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2401 > 1. Create loan product with following datasets, > Terms > Terms vary based on loan cycle : false > Principal: 10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate: 1 ( Min: , Max) Per month > Minimum days between disbursal and first repayment date > Settings > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Arrears Tolerance > Repayment Strategy Overdue/Due Fee/Int,Principal > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amount No > Variable Installments (Min:0 , Max:365) > Interest Recalculation > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01 October 2015 > Is Arrears recognization based on original schedule No > 2. Create a client and submit new loan application on 01 October 2015. > 3. Click on More -> Edit repayment schedule in which delete repayment for 01 > November 2015 and click on validate and submit button. > 4. Approve and disburse loan on 01 October 2015. > 5. Make repayment on 15 December 2015. > > In Overdue/Due Fee/Int,Principal repayment strategy one entry on 15 > > December 2015 should get created, which is not getting getting created. > > Interest should get calculated upto 14 December 2015. (Disbursement date 01 > > October 2015 and first repayment is doing on 15 December 2015). > Attachments: https://mifosforge.jira.com/browse/MIFOSX-2401 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-12) For Overdue/Due Fee/Int,Principal strategy with variable installment, late repayment is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-12: - Labels: Volunteer p1 (was: V p1) > For Overdue/Due Fee/Int,Principal strategy with variable installment, late > repayment is not working as expected > --- > > Key: FINERACT-12 > URL: https://issues.apache.org/jira/browse/FINERACT-12 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p1 > Fix For: 1.4.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2401 > 1. Create loan product with following datasets, > Terms > Terms vary based on loan cycle : false > Principal: 10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate: 1 ( Min: , Max) Per month > Minimum days between disbursal and first repayment date > Settings > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Arrears Tolerance > Repayment Strategy Overdue/Due Fee/Int,Principal > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amount No > Variable Installments (Min:0 , Max:365) > Interest Recalculation > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01 October 2015 > Is Arrears recognization based on original schedule No > 2. Create a client and submit new loan application on 01 October 2015. > 3. Click on More -> Edit repayment schedule in which delete repayment for 01 > November 2015 and click on validate and submit button. > 4. Approve and disburse loan on 01 October 2015. > 5. Make repayment on 15 December 2015. > > In Overdue/Due Fee/Int,Principal repayment strategy one entry on 15 > > December 2015 should get created, which is not getting getting created. > > Interest should get calculated upto 14 December 2015. (Disbursement date 01 > > October 2015 and first repayment is doing on 15 December 2015). > Attachments: https://mifosforge.jira.com/browse/MIFOSX-2401 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-13) Multi-tranche Loan repayment on 2nd tranche incorrect
[ https://issues.apache.org/jira/browse/FINERACT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712140#comment-16712140 ] Edward Cable commented on FINERACT-13: -- [~santoshmath] this still exists correct? > Multi-tranche Loan repayment on 2nd tranche incorrect > - > > Key: FINERACT-13 > URL: https://issues.apache.org/jira/browse/FINERACT-13 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p1 > Fix For: 1.3.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2398 - See for attachments > 1. Create a loan product with following data sets, > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max) Per month > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyPenalties, Fees, Interest, Principal order > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Sep-15 > Enable Multiple DisbursalsTRUE > Maximum Tranche count 2 > Maximum allowed outstanding balance 1 > 2. Create specified due date charge 1% of amount and attache to the above > loan product, > 3. Submit new loan application for a client on 01 September 2015 with first > tranche of 5000 on same date and second tranche on 01 November 2015 and > amount 5000. Add specified due date charge date as 15 September 2015. > 4. Make repayment on 01 October 2015 in which charge applied on 15 September > 2015 got collected and amount as 50 (1% of disbursed amount). > 5. Disburse 2nd tranche as 5000 on 01 November 2015. > > In the repayment schedule 50 is displaying as balance in 01 October 2015 > > repayment. > > Application Should not allowed to modify or apply charge for the repayment > > which is already paid -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-19) On time loan payment, Overdue Charge should be principal ony
[ https://issues.apache.org/jira/browse/FINERACT-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-19: - Labels: Volunteer p1 (was: p1) > On time loan payment, Overdue Charge should be principal ony > > > Key: FINERACT-19 > URL: https://issues.apache.org/jira/browse/FINERACT-19 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p1 > Fix For: 1.3.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2400 - see for attachments > 1. Create a simple loan product with with monthly repayment and overdue > charge as flat 100 attached. > 2. Create a client and submit new loan application for a client on 01 > September 2015 approve and disburse on same date. > 3. Execute scheduler job "Apply penalty for overdue loans". > 4. Now overdue charge got applied for 01 October 2015, 01 November 2015 and > 01 December 2015 repayments. > 5. Make back dated repayment with the amount displayed in repayment schedule > on 01 October 2015. > Expected behavior: > .Since the repayment is done on time the extra amount ie 100 paid should go > to the principal only. > Actual behavior: > The extra amount 100 is getting collected as advance payment for the > immediate next repayment. > Also for the 1st of January the penalty displayed wrongly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-13) Multi-tranche Loan repayment on 2nd tranche incorrect
[ https://issues.apache.org/jira/browse/FINERACT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-13: - Labels: Volunteer p1 (was: p1) > Multi-tranche Loan repayment on 2nd tranche incorrect > - > > Key: FINERACT-13 > URL: https://issues.apache.org/jira/browse/FINERACT-13 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p1 > Fix For: 1.3.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2398 - See for attachments > 1. Create a loan product with following data sets, > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max) > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max) Per month > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyPenalties, Fees, Interest, Principal order > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Sep-15 > Enable Multiple DisbursalsTRUE > Maximum Tranche count 2 > Maximum allowed outstanding balance 1 > 2. Create specified due date charge 1% of amount and attache to the above > loan product, > 3. Submit new loan application for a client on 01 September 2015 with first > tranche of 5000 on same date and second tranche on 01 November 2015 and > amount 5000. Add specified due date charge date as 15 September 2015. > 4. Make repayment on 01 October 2015 in which charge applied on 15 September > 2015 got collected and amount as 50 (1% of disbursed amount). > 5. Disburse 2nd tranche as 5000 on 01 November 2015. > > In the repayment schedule 50 is displaying as balance in 01 October 2015 > > repayment. > > Application Should not allowed to modify or apply charge for the repayment > > which is already paid -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-19) On time loan payment, Overdue Charge should be principal ony
[ https://issues.apache.org/jira/browse/FINERACT-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712138#comment-16712138 ] Edward Cable commented on FINERACT-19: -- [~santoshmath] Does this issue still exist in current release? > On time loan payment, Overdue Charge should be principal ony > > > Key: FINERACT-19 > URL: https://issues.apache.org/jira/browse/FINERACT-19 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p1 > Fix For: 1.3.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2400 - see for attachments > 1. Create a simple loan product with with monthly repayment and overdue > charge as flat 100 attached. > 2. Create a client and submit new loan application for a client on 01 > September 2015 approve and disburse on same date. > 3. Execute scheduler job "Apply penalty for overdue loans". > 4. Now overdue charge got applied for 01 October 2015, 01 November 2015 and > 01 December 2015 repayments. > 5. Make back dated repayment with the amount displayed in repayment schedule > on 01 October 2015. > Expected behavior: > .Since the repayment is done on time the extra amount ie 100 paid should go > to the principal only. > Actual behavior: > The extra amount 100 is getting collected as advance payment for the > immediate next repayment. > Also for the 1st of January the penalty displayed wrongly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-99) Waiving of charge results in an incorrect account balance status
[ https://issues.apache.org/jira/browse/FINERACT-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable closed FINERACT-99. Resolution: Cannot Reproduce > Waiving of charge results in an incorrect account balance status > > > Key: FINERACT-99 > URL: https://issues.apache.org/jira/browse/FINERACT-99 > Project: Apache Fineract > Issue Type: Bug >Reporter: Emmanuel Nnaa >Assignee: Markus Geiss >Priority: Major > Labels: confirm, p1 > Fix For: 1.3.0 > > > Example affected loan: > - The summary for this loan shows it as active: Contract > Paid, however > Outstanding balance is 0. > - When checking the Transactions the balance is -67 (which suggests overpaid). > - And finally the "Disbursed Loan Report" reports an overdue status with a > balance of 0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-146) In Demo version loans awaiting for approval is not getting displayed properly under Checker in box and tasks
[ https://issues.apache.org/jira/browse/FINERACT-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712134#comment-16712134 ] Edward Cable commented on FINERACT-146: --- [~santoshmath] Can you try to reproduce this? > In Demo version loans awaiting for approval is not getting displayed properly > under Checker in box and tasks > > > Key: FINERACT-146 > URL: https://issues.apache.org/jira/browse/FINERACT-146 > Project: Apache Fineract > Issue Type: Bug >Reporter: subramanyasn >Assignee: Markus Geiss >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > Attachments: Mifos X Client 2016-04-29 04-17-41.png, Mifos X Client > 2016-04-29 04-19-11.png > > > In demo version after clicking on the checker inbox and tasks, the recently > submitted loan awaiting for approval is not getting displayed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-229) As admin of the system, I should be able to reset password for other users
[ https://issues.apache.org/jira/browse/FINERACT-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-229: -- Labels: Volunteer gsoc p1 (was: gsoc p1) > As admin of the system, I should be able to reset password for other users > -- > > Key: FINERACT-229 > URL: https://issues.apache.org/jira/browse/FINERACT-229 > Project: Apache Fineract > Issue Type: Improvement > Components: User Management >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p1 > Fix For: 1.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712126#comment-16712126 ] Edward Cable commented on FINERACT-276: --- [~Shruthi M R] Can we try to explore a fix for this? > 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 >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > 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 (v7.6.3#76005)
[jira] [Updated] (FINERACT-302) Principal Threshold (%) for Last Instalment is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-302: -- Labels: Volunteer fineract-gci p1 (was: fineract-gci p1) > Principal Threshold (%) for Last Instalment is not working as expected > -- > > Key: FINERACT-302 > URL: https://issues.apache.org/jira/browse/FINERACT-302 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, fineract-gci, p1 > Fix For: 1.3.0 > > 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 (v7.6.3#76005)
[jira] [Resolved] (FINERACT-270) Unable to waive all Loan charges
[ https://issues.apache.org/jira/browse/FINERACT-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable resolved FINERACT-270. --- Resolution: Fixed Fix Version/s: (was: 1.3.0) 1.0.0 Fixed June 2017 > Unable to waive all Loan charges > > > Key: FINERACT-270 > URL: https://issues.apache.org/jira/browse/FINERACT-270 > Project: Apache Fineract > Issue Type: Bug > Components: Loan > Environment: Reproducible on demo.openmf.org. > Create new client Loan with FINERACT_7-MIFOS_2495 >Reporter: Abdul Aziz Ali >Assignee: Shaik Nazeer Hussain >Priority: Trivial > Labels: p1 > Fix For: 1.0.0 > > Attachments: pruned_catalina.log > > > Create Loan and Charge similar to FINERACT-7 > > (verbatim from FINERACT-7) > 1. Create Installment fee for a loan as 100-Flat-Regular. > 2. Create loan product with following datasets and attache above installment > fee to that. > Terms vary based on loan cycle : FALSE > Principal:10,000 ( Min: , Max : ) > Number of Repayments: 12 ( Min: , Max > Repay Every: 1 Months > Nominal Interest Rate:1 ( Min: , Max Per month > Minimum days between disbursal and first repayment date > Amortization Equal installments > Interest Method Declining Balance > Interest Calculation Period Daily > Repayment StrategyOverdue/Due Fee/Int,Principal > Account moves out of NPA only after all arrears have been cleared?No > Days in year Actual > Days in month Actual > Principal Threshold (%) for Last Instalment 0 > Allow fixing of the installment amountNo > Interest Recalculation > 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 Daily > Frequency Interval for recalculation 1 > Frequency Date for recalculation 01-Jan-15 > Is Arrears recognization based on original schedule:No. > 3. Submit new loan application on 01 October 2015. Approve and disburse loan > on same date. > 4. Click on waive charge and select for 1st repayment. > 5. Repayment schedule generated after waive charge is not proper > >Waive charge is happening not for first installment instead for other > >installment it is happening. > 6. For first repayment the due is getting displayed. > > 7. Keep waiving all charges until the last one > The last one does not get waived nor does the Exception get raised to the UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FINERACT-271) Not able to Writeoff the loan if the writeoff date = any repayment date in periodic accrual
[ https://issues.apache.org/jira/browse/FINERACT-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable resolved FINERACT-271. --- Resolution: Fixed Fixed per comments from Nazeer. > Not able to Writeoff the loan if the writeoff date = any repayment date in > periodic accrual > --- > > Key: FINERACT-271 > URL: https://issues.apache.org/jira/browse/FINERACT-271 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: fineract-gci, p1 > Fix For: 1.3.0 > > Attachments: 1.png, 2.png > > > As reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1152. > Original Description: > 1. Create a loan product with periodic accrual accounting. > 2. Create a client and attach the above mentioned loan product to that client. > 3. Submit a new loan application on 02 April 2014 approve and disburse on the > same date. > 4. Click on system -> Scheduler job -> Run the job " Add Accrual > Transactions". > 5. In the above mentioned loan account page click on the Transactions - in > which accrual accounting with respect to each repayment is displayed. > 6. Click on "More" tab and click on Writeoff button. > 7. In loan writeoff page enter date as latest repayment date. (As displayed > in Transactions page) and click on submit button. > Expected result: > After the loan disbursement is done on any point of time it should allow to > writeoff the loan after last Transaction happened.(Here no transaction > happened after disbursement) > Actual Result: > Not able to writeoff the Loan since displayed error message as "The date of > the writeoff transaction must occur after the last transaction made against > this loan." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-281) Periodic accrual on a particular day is not calculating as expected
[ https://issues.apache.org/jira/browse/FINERACT-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712124#comment-16712124 ] Edward Cable commented on FINERACT-281: --- [~santoshmath] Have we confirmed this issue? > Periodic accrual on a particular day is not calculating as expected > --- > > Key: FINERACT-281 > URL: https://issues.apache.org/jira/browse/FINERACT-281 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: Volunteer, confirm, p1 > Fix For: 1.3.0 > > Attachments: Scr-339.png, Scr-340.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1487 > Original Description: > If Loan disbursed on 05 june 2014, first repayment falls on 19 june 2014 and > If periodic accrual on a particular day ie on 30 june 2014 is run then > accrued interest between 19 june 2014 to 30 june 2014 should be calculated > and displayed instead it is displaying accrued interest from 05 june 2014 to > 30 june 2014. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-284) Collection Sheet as a tool for collecting savings
[ https://issues.apache.org/jira/browse/FINERACT-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712123#comment-16712123 ] Edward Cable commented on FINERACT-284: --- [~santoshmath] Should we close this as won't fix? Do we now support savings and/or recurring deposits collection in the collection sheet? > Collection Sheet as a tool for collecting savings > - > > Key: FINERACT-284 > URL: https://issues.apache.org/jira/browse/FINERACT-284 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p1 > Fix For: 1.3.0 > > > Reported by Okeleke Mike at https://mifosforge.jira.com/browse/MIFOSX-1558 > Original Description: > I have long been an advocate of the collection sheet, I love the concept and > the idea but I still wonder why it’s only use as always been on loans > collection. I think with the inclusion of Mandatory Deposit (fixed & > recurrent savings) into the MifosX platform it can also easily collect > savings contribution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-307) Accruals accounting does not accrue income on loans closed prematurely
[ https://issues.apache.org/jira/browse/FINERACT-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712119#comment-16712119 ] Edward Cable commented on FINERACT-307: --- [~vishwasbabu] [~ashok] Do you know if this has been fixed in the build Conflux uses for Finflux? > 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: Shaik Nazeer Hussain >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > 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 (v7.6.3#76005)
[jira] [Commented] (FINERACT-336) Fund Mapping page Points to Advanced Search page
[ https://issues.apache.org/jira/browse/FINERACT-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711959#comment-16711959 ] Edward Cable commented on FINERACT-336: --- [~Shruthi M R] can we at least update the shortcuts and make links point where they should as a near-term fix? > 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: Edward Cable >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.3.0 > > 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 (v7.6.3#76005)
[jira] [Commented] (FINERACT-336) Fund Mapping page Points to Advanced Search page
[ https://issues.apache.org/jira/browse/FINERACT-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711963#comment-16711963 ] Edward Cable commented on FINERACT-336: --- Shouldn't this ad-hoc search be linked to as advanced search? [~vishwasbabu] thoughts? > 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: Edward Cable >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.3.0 > > 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 (v7.6.3#76005)
[jira] [Updated] (FINERACT-348) Issues when doing a "Close-As-Rescheduled" on a loan
[ https://issues.apache.org/jira/browse/FINERACT-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-348: -- Fix Version/s: (was: 1.3.0) 1.4.0 > 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: gsoc, p1 > Fix For: 1.4.0 > > > 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 (v7.6.3#76005)
[jira] [Commented] (FINERACT-466) For the loans without Interest Recalculation, Prepay Loan is collecting all installment Fees in stead of collecting installment fees until the prepay date
[ https://issues.apache.org/jira/browse/FINERACT-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711939#comment-16711939 ] Edward Cable commented on FINERACT-466: --- [~santoshmath] Isn't this a bug? > For the loans without Interest Recalculation, Prepay Loan is collecting all > installment Fees in stead of collecting installment fees until the prepay date > -- > > Key: FINERACT-466 > URL: https://issues.apache.org/jira/browse/FINERACT-466 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Loan >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > > 1. Create a loan product without Interest recalculation,monthly repayment, > Equal Installments, Declining balance and 12 repayments with installment fee > 100((flat, monthly) attached. > 2. Disburse the loan on 01 January 2017. > 3 Prepay the loan on 15 February 2017. > > Expected Result: The installment fee should be collected: 100 > >Actual Result: The installment fee getting collected: 1200(all installment > >fees) > P.S: This issue doesn't exist with loans having interest recalculation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-363) Penalty to be attached/updated to a loan account which was created when a loan product had no penalty/penalty with different amount
[ https://issues.apache.org/jira/browse/FINERACT-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711946#comment-16711946 ] Edward Cable commented on FINERACT-363: --- [~Shruthi M R] have we begun work on this issue? > Penalty to be attached/updated to a loan account which was created when a > loan product had no penalty/penalty with different amount > > > Key: FINERACT-363 > URL: https://issues.apache.org/jira/browse/FINERACT-363 > Project: Apache Fineract > Issue Type: Bug > Components: Charges >Reporter: Mexina Daniel >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > 1. Create a loan product without overdue charges (penalty) in Admin -> > Product -> Loan Product -> Create Loan Product > 2. Apply a loan account of that loan product to a client at Clients -> View > Client -> New Loan > 3. Approve a loan, disburse and make few repayments > 4. Then create a charge which is overdue (is penalty) in Admin -> Products -> > Charges -> Create Charge > 5. Go to that loan product and attach an overdue charge > What happens: > The applied penalty is also attached to that loan which was created before > this update > Expected: > The loan account should not be updated if it was created before the change, > the penalty should be applied to loan accounts that will be applied after > update of loan product. > 6. Update a penalty and change it's amount > What happens: > All loan accounts that the penalty is applied, the amount of the penalty will > also change. > Expected: > The amount of the penalty should not change to the loan accounts that were > attached before the update of the penalty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-381) Repayment schedule mismatch before approval and after approval when two consecutive holidays comes on repayment
[ https://issues.apache.org/jira/browse/FINERACT-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable closed FINERACT-381. - Resolution: Works for Me > Repayment schedule mismatch before approval and after approval when two > consecutive holidays comes on repayment > --- > > Key: FINERACT-381 > URL: https://issues.apache.org/jira/browse/FINERACT-381 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Avinash Dalvi >Assignee: Markus Geiss >Priority: Critical > Labels: p1 > Fix For: 1.3.0 > > Attachments: image001.jpg, image002.jpg > > > Have configured a loan product with declining balance, recalculate > interest, and frequency for recalculate outstanding principal as ?same as > repayment period?. System is configured to have payments due on non working > days to be moved to next working day. Found that the date when the > principal is recalculated is not the same date as expected EMI / repayment > date in case the repayment date is a holiday. > Loan configuration screen shot: > The repayment schedule comes like below: The interest computed of 3,682 is > on the principal of 200,000 rather than 134,894, as the outstanding > principal calculation was done based on principal on 12th Feb and not 13th > Feb which is the date of EMI payment. Please refer to the screen shot > below. Same happens for interest of 2,661 which is based on 134,894 rather > than 69,262. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-381) Repayment schedule mismatch before approval and after approval when two consecutive holidays comes on repayment
[ https://issues.apache.org/jira/browse/FINERACT-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711942#comment-16711942 ] Edward Cable commented on FINERACT-381: --- [~santoshmath] if we are still unable to reproduce the error, I will close this. > Repayment schedule mismatch before approval and after approval when two > consecutive holidays comes on repayment > --- > > Key: FINERACT-381 > URL: https://issues.apache.org/jira/browse/FINERACT-381 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Avinash Dalvi >Assignee: Markus Geiss >Priority: Critical > Labels: p1 > Fix For: 1.3.0 > > Attachments: image001.jpg, image002.jpg > > > Have configured a loan product with declining balance, recalculate > interest, and frequency for recalculate outstanding principal as ?same as > repayment period?. System is configured to have payments due on non working > days to be moved to next working day. Found that the date when the > principal is recalculated is not the same date as expected EMI / repayment > date in case the repayment date is a holiday. > Loan configuration screen shot: > The repayment schedule comes like below: The interest computed of 3,682 is > on the principal of 200,000 rather than 134,894, as the outstanding > principal calculation was done based on principal on 12th Feb and not 13th > Feb which is the date of EMI payment. Please refer to the screen shot > below. Same happens for interest of 2,661 which is based on 134,894 rather > than 69,262. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-463) Dashboard showing no data for 'Amount Collected for Today' even though there are trasactions today
[ https://issues.apache.org/jira/browse/FINERACT-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-463: -- Fix Version/s: (was: 1.3.0) 1.4.0 > Dashboard showing no data for 'Amount Collected for Today' even though there > are trasactions today > > > Key: FINERACT-463 > URL: https://issues.apache.org/jira/browse/FINERACT-463 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gci, gsoc2017, p1 > Fix For: 1.4.0 > > Attachments: dashboard.png > > > Reported by Onyedikachi Nwosu > 1. Create a new office and create a client under the new office. > 2. perform a deposit of 10,000 to a savings account and issued a loan to the > value of 10,000 for the same client. > As can be seen from the attached screenshot, On the dashboard, Amount > Disbursed for Today reflects the 10,000 loan, but the Amount Collected for > Today does not reflect 10,000 savings made. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-463) Dashboard showing no data for 'Amount Collected for Today' even though there are trasactions today
[ https://issues.apache.org/jira/browse/FINERACT-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-463: -- Labels: gci gsoc2017 p1 (was: gsoc2017 p1) > Dashboard showing no data for 'Amount Collected for Today' even though there > are trasactions today > > > Key: FINERACT-463 > URL: https://issues.apache.org/jira/browse/FINERACT-463 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gci, gsoc2017, p1 > Fix For: 1.4.0 > > Attachments: dashboard.png > > > Reported by Onyedikachi Nwosu > 1. Create a new office and create a client under the new office. > 2. perform a deposit of 10,000 to a savings account and issued a loan to the > value of 10,000 for the same client. > As can be seen from the attached screenshot, On the dashboard, Amount > Disbursed for Today reflects the 10,000 loan, but the Amount Collected for > Today does not reflect 10,000 savings made. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-478) Savings overdraft fee with charge time type 'overdraft fee' and charge calculation '%amount' is not working
[ https://issues.apache.org/jira/browse/FINERACT-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711934#comment-16711934 ] Edward Cable commented on FINERACT-478: --- [~Shruthi M R] How related is this to Fineract-478? > Savings overdraft fee with charge time type 'overdraft fee' and charge > calculation '%amount' is not working > --- > > Key: FINERACT-478 > URL: https://issues.apache.org/jira/browse/FINERACT-478 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Savings >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > > 1. Go to charges and select charge applied to 'Savings and deposits' > 2. Fill other required inputs with > Charge Time type: overdraft fee > Charge calculation : % amount. > Amount : 1 > > After submission , it is throwing error: > > "validation.msg.charges.charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivity" > Expected: > 1.This feature of overdraft fee with charge calculation as % amount need to > be implemented. > 2. Until the feature is implemented, the following proper error message > should be thrown in stead of above mentioned: > ""validation.msg: > charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivityand > yet to be implemented for overdraft fee" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-440) Include runningBalance, appUser in m_share_account_transactions table.
[ https://issues.apache.org/jira/browse/FINERACT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711916#comment-16711916 ] Edward Cable commented on FINERACT-440: --- [~Ippez] can you share more details of what parameters are needed. Is this to generate a report? > Include runningBalance, appUser in m_share_account_transactions table. > -- > > Key: FINERACT-440 > URL: https://issues.apache.org/jira/browse/FINERACT-440 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gci, gsoc, p2 > Fix For: 1.4.0 > > > Include the two parameters runningBalance, appUser in > m_share_account_transactions to be used to generate Share Transaction > Statement. Currently its not posible to generate standard statement since > runningBalance is missing and kind of hard to determine it from current Share > Transaction table -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (FINERACT-504) Support of rescheduling of loan for the loan products with Interest Recalculation enabled
[ https://issues.apache.org/jira/browse/FINERACT-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable reopened FINERACT-504: --- > Support of rescheduling of loan for the loan products with Interest > Recalculation enabled > - > > Key: FINERACT-504 > URL: https://issues.apache.org/jira/browse/FINERACT-504 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p1 > > Currently loans with interest recalculation enabled, can not be rescheduled. > The support for the same needed in near future. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-504) Support of rescheduling of loan for the loan products with Interest Recalculation enabled
[ https://issues.apache.org/jira/browse/FINERACT-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable closed FINERACT-504. - Resolution: Fixed Fix Version/s: (was: 1.3.0) > Support of rescheduling of loan for the loan products with Interest > Recalculation enabled > - > > Key: FINERACT-504 > URL: https://issues.apache.org/jira/browse/FINERACT-504 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p1 > > Currently loans with interest recalculation enabled, can not be rescheduled. > The support for the same needed in near future. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-504) Support of rescheduling of loan for the loan products with Interest Recalculation enabled
[ https://issues.apache.org/jira/browse/FINERACT-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable closed FINERACT-504. - Resolution: Duplicate > Support of rescheduling of loan for the loan products with Interest > Recalculation enabled > - > > Key: FINERACT-504 > URL: https://issues.apache.org/jira/browse/FINERACT-504 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p1 > > Currently loans with interest recalculation enabled, can not be rescheduled. > The support for the same needed in near future. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (FINERACT-504) Support of rescheduling of loan for the loan products with Interest Recalculation enabled
[ https://issues.apache.org/jira/browse/FINERACT-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable reopened FINERACT-504: --- > Support of rescheduling of loan for the loan products with Interest > Recalculation enabled > - > > Key: FINERACT-504 > URL: https://issues.apache.org/jira/browse/FINERACT-504 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > > Currently loans with interest recalculation enabled, can not be rescheduled. > The support for the same needed in near future. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-505) Loan Tranche Details should be captured in Bulk JLG loan application.
[ https://issues.apache.org/jira/browse/FINERACT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-505: -- Labels: Volunteer gsoc p2 (was: gsoc p1) > Loan Tranche Details should be captured in Bulk JLG loan application. > - > > Key: FINERACT-505 > URL: https://issues.apache.org/jira/browse/FINERACT-505 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > Fix For: 1.4.0 > > > Presently, there is no fields to capture multi-tranche details in 'Bulk JLG > loan application' . Therefore, Bulk JLG loan application doesn't support > multi-tranche loan products. The current temperory fix is, the loan products > with multi-tranche aren't displaying in drop-down menu of 'Bulk JLG loan > application'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-505) Loan Tranche Details should be captured in Bulk JLG loan application.
[ https://issues.apache.org/jira/browse/FINERACT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-505: -- Fix Version/s: (was: 1.3.0) 1.4.0 > Loan Tranche Details should be captured in Bulk JLG loan application. > - > > Key: FINERACT-505 > URL: https://issues.apache.org/jira/browse/FINERACT-505 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > Fix For: 1.4.0 > > > Presently, there is no fields to capture multi-tranche details in 'Bulk JLG > loan application' . Therefore, Bulk JLG loan application doesn't support > multi-tranche loan products. The current temperory fix is, the loan products > with multi-tranche aren't displaying in drop-down menu of 'Bulk JLG loan > application'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-505) Loan Tranche Details should be captured in Bulk JLG loan application.
[ https://issues.apache.org/jira/browse/FINERACT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711926#comment-16711926 ] Edward Cable commented on FINERACT-505: --- [~Shruthi M R] What is level of effort to support this? > Loan Tranche Details should be captured in Bulk JLG loan application. > - > > Key: FINERACT-505 > URL: https://issues.apache.org/jira/browse/FINERACT-505 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gsoc, p2 > Fix For: 1.4.0 > > > Presently, there is no fields to capture multi-tranche details in 'Bulk JLG > loan application' . Therefore, Bulk JLG loan application doesn't support > multi-tranche loan products. The current temperory fix is, the loan products > with multi-tranche aren't displaying in drop-down menu of 'Bulk JLG loan > application'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-513) Reverse Overdue Charges Application
[ https://issues.apache.org/jira/browse/FINERACT-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-513: -- Fix Version/s: (was: 1.3.0) 1.4.0 > Reverse Overdue Charges Application > --- > > Key: FINERACT-513 > URL: https://issues.apache.org/jira/browse/FINERACT-513 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Loan, System >Affects Versions: 1.0.0 >Reporter: Adriana Pinto >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p1 > Fix For: 1.4.0 > > Attachments: FINERACT-513.pdf > > > We've been working on having a complete functionality of our approach, but we > got an issue at the moment of applying overdue charges when running the job: > Is there any workaround to reverse the overdue charges application? > This is necessary, because the overdue charges are being applied daily, but > if the repayment is made before applying the charges, but it is not > registered at the system, we need to reverse the calculation and "remove" > this charges from the final outstanding. > +*Current Business behaviour*+: When the client makes a repayment, it might > not be registered in the system until some days or weeks later, then the > overdue charges if are applied daily, have to be reversed from de current > date until the date the repayment was done. > Then, it is the approach we are looking for. > We had already figured out the "Waiving charges" process, but it would work > better if there was a job doing the contrary process of applying overdue > charges, like "Reverse overdue charges" by date or any moment in a specified > time. > **The attachment (FINERACT-513.pdf) shows the funtionality in a more specific > way. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-513) Reverse Overdue Charges Application
[ https://issues.apache.org/jira/browse/FINERACT-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711922#comment-16711922 ] Edward Cable commented on FINERACT-513: --- [~adripinto] Has the BOWPI team still been working on this? > Reverse Overdue Charges Application > --- > > Key: FINERACT-513 > URL: https://issues.apache.org/jira/browse/FINERACT-513 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Loan, System >Affects Versions: 1.0.0 >Reporter: Adriana Pinto >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > Attachments: FINERACT-513.pdf > > > We've been working on having a complete functionality of our approach, but we > got an issue at the moment of applying overdue charges when running the job: > Is there any workaround to reverse the overdue charges application? > This is necessary, because the overdue charges are being applied daily, but > if the repayment is made before applying the charges, but it is not > registered at the system, we need to reverse the calculation and "remove" > this charges from the final outstanding. > +*Current Business behaviour*+: When the client makes a repayment, it might > not be registered in the system until some days or weeks later, then the > overdue charges if are applied daily, have to be reversed from de current > date until the date the repayment was done. > Then, it is the approach we are looking for. > We had already figured out the "Waiving charges" process, but it would work > better if there was a job doing the contrary process of applying overdue > charges, like "Reverse overdue charges" by date or any moment in a specified > time. > **The attachment (FINERACT-513.pdf) shows the funtionality in a more specific > way. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-518) Share Transaction doesn't capture user ID
[ https://issues.apache.org/jira/browse/FINERACT-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-518: -- Labels: gci p1 (was: p1) > Share Transaction doesn't capture user ID > - > > Key: FINERACT-518 > URL: https://issues.apache.org/jira/browse/FINERACT-518 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Critical > Labels: gci, p1 > Fix For: 1.3.0 > > > In m_share_account_transactions table there is no column for appuser_id for > capturing the user id of whose so ever has done a transaction, be it Share > purchase, Share Redeem hence auditing share transactions is hard -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-440) Include runningBalance, appUser in m_share_account_transactions table.
[ https://issues.apache.org/jira/browse/FINERACT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-440: -- Labels: Volunteer gci gsoc p2 (was: Volunteer gsoc p2) > Include runningBalance, appUser in m_share_account_transactions table. > -- > > Key: FINERACT-440 > URL: https://issues.apache.org/jira/browse/FINERACT-440 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gci, gsoc, p2 > Fix For: 1.4.0 > > > Include the two parameters runningBalance, appUser in > m_share_account_transactions to be used to generate Share Transaction > Statement. Currently its not posible to generate standard statement since > runningBalance is missing and kind of hard to determine it from current Share > Transaction table -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-440) Include runningBalance, appUser in m_share_account_transactions table.
[ https://issues.apache.org/jira/browse/FINERACT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-440: -- Fix Version/s: 1.4.0 > Include runningBalance, appUser in m_share_account_transactions table. > -- > > Key: FINERACT-440 > URL: https://issues.apache.org/jira/browse/FINERACT-440 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Reporter: Ippez Roberts >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gci, gsoc, p2 > Fix For: 1.4.0 > > > Include the two parameters runningBalance, appUser in > m_share_account_transactions to be used to generate Share Transaction > Statement. Currently its not posible to generate standard statement since > runningBalance is missing and kind of hard to determine it from current Share > Transaction table -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-534) Want to Group Wise and Center Wise Accounting
[ https://issues.apache.org/jira/browse/FINERACT-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711904#comment-16711904 ] Edward Cable commented on FINERACT-534: --- [~raakeshtomar] Could you provide a design of what you'd like to see in this report? > Want to Group Wise and Center Wise Accounting > -- > > Key: FINERACT-534 > URL: https://issues.apache.org/jira/browse/FINERACT-534 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.0.0 >Reporter: Rakesh Tomar >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > Fix For: 1.4.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-527) Enhancing Notification Framework
[ https://issues.apache.org/jira/browse/FINERACT-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711911#comment-16711911 ] Edward Cable commented on FINERACT-527: --- [~courage] I thought your work had been merged in? It hasn't? > Enhancing Notification Framework > > > Key: FINERACT-527 > URL: https://issues.apache.org/jira/browse/FINERACT-527 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization, User Management >Affects Versions: 1.1.0 >Reporter: Courage Angeh >Priority: Major > Fix For: 1.3.0 > > > *Workdone* > * Access if activeMQ is active, if so enable activeMQ else use Spring's built > in tool called Spring Event > * User subscription to topic when user account is created > * Create topics for an organization based on roles in that organization, when > the organization is created > * Upgrade process of user notification > * Migration script - topic, topic subscription models for new and already > existing users and organizations > * Update user subscription on user transfer and/or update of user's permission > * Update topic details when entity details updates > * Update topic details when member type are updated at the system level > * Unit test topic-subscriber model -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-532) Issue in Address section of Client creation page
[ https://issues.apache.org/jira/browse/FINERACT-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711907#comment-16711907 ] Edward Cable commented on FINERACT-532: --- [~Shruthi M R] Have we looked into the fix for this issue? Do we have an estimate for the level of effort? > Issue in Address section of Client creation page > > > Key: FINERACT-532 > URL: https://issues.apache.org/jira/browse/FINERACT-532 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.0.0 >Reporter: Chanda Aparna >Assignee: Markus Geiss >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > Attachments: Address Issue.png > > > Multiple addresses are created during client creation. Please try to get > validation error during client creation. It will create multiple addresses. > Client (Test Client 12334 Client #: 03272) created in Demo site has 4 > times Address created. > This issue is from the current version of demo site (Version > 17.07.01.RELEASE). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-520) The field for "is staff" in the client creation does not store data
[ https://issues.apache.org/jira/browse/FINERACT-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-520: -- Fix Version/s: 1.3.0 > The field for "is staff" in the client creation does not store data > > > Key: FINERACT-520 > URL: https://issues.apache.org/jira/browse/FINERACT-520 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Mexina Daniel >Assignee: Markus Geiss >Priority: Major > Labels: client, gci, p2 > Fix For: 1.3.0 > > > When you create a client and select the field "is staff", it is selected but > after submission and come again to edit, you find the field not selected, > which shows the value was not stored. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-520) The field for "is staff" in the client creation does not store data
[ https://issues.apache.org/jira/browse/FINERACT-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-520: -- Labels: client gci p2 (was: client p2) > The field for "is staff" in the client creation does not store data > > > Key: FINERACT-520 > URL: https://issues.apache.org/jira/browse/FINERACT-520 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Mexina Daniel >Assignee: Markus Geiss >Priority: Major > Labels: client, gci, p2 > Fix For: 1.3.0 > > > When you create a client and select the field "is staff", it is selected but > after submission and come again to edit, you find the field not selected, > which shows the value was not stored. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-534) Want to Group Wise and Center Wise Accounting
[ https://issues.apache.org/jira/browse/FINERACT-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-534: -- Fix Version/s: (was: 1.3.0) 1.4.0 > Want to Group Wise and Center Wise Accounting > -- > > Key: FINERACT-534 > URL: https://issues.apache.org/jira/browse/FINERACT-534 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.0.0 >Reporter: Rakesh Tomar >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > Fix For: 1.4.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-535) Allow the same name of teller if its from different branchs
[ https://issues.apache.org/jira/browse/FINERACT-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-535: -- Labels: features gci gsoc p1 (was: features gsoc p1) > Allow the same name of teller if its from different branchs > --- > > Key: FINERACT-535 > URL: https://issues.apache.org/jira/browse/FINERACT-535 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Reporter: Mexina Daniel >Assignee: Markus Geiss >Priority: Major > Labels: features, gci, gsoc, p1 > Fix For: 1.3.0 > > > For now when you create a teller with the name which already exist even from > another branch it gives an error of duplicate name > Think of the institution which have the same format of naming its tellers > like Teller1, Teller2, etc > and it has two branches. > The system should allow to create Teller1 of branch1 and Teller1 of branch2. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-574) Issues related to share Account Creation
[ https://issues.apache.org/jira/browse/FINERACT-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711873#comment-16711873 ] Edward Cable commented on FINERACT-574: --- [~Shruthi M R] Can you resolve this is the merged PR fixes it? > Issues related to share Account Creation > > > Key: FINERACT-574 > URL: https://issues.apache.org/jira/browse/FINERACT-574 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: gci, gsoc, p1 > Fix For: 1.3.0 > > Attachments: Screenshot from 2017-12-12 21-05-47.png > > > 1. Create Share Product with Accounting Enabled > 2. Create a share charge with type 'Share Purchase' ,'Flat' amount $2. > 3. Create and activate savings account for client which is needed to link > with share account > 4. Create a share Account application for current date using above product > and charge and number of shares issued as 10 , each share price as $0.5. > > Once you 'Submit' the share application journal entries are created > > (including charge) even though share account is not yet approved/activated. > >Approve the share account and again duplicate jounal entries are created. > >If share account application is attached with 'Share Activation Fee' , upon > >submission of share account application, if we check 'Transaction Overview' > >tab, it shows 'Activation Fee' is received even though share account is not > >activated. Same is updated in the database > >table,"m_share_account_charge_paid_by". But under the 'Charges' tab, it > >shows Outstanding(which is correct). > The all scenarios can be tested here by modifying application and using the > charges > 'Share Purchase Fee' or 'Share Activation Fee' > https://staging.openmf.org/#/viewshareaccount/5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-536) Report categories are inconsistent and causing reports to go missing in the drop-down
[ https://issues.apache.org/jira/browse/FINERACT-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711886#comment-16711886 ] Edward Cable commented on FINERACT-536: --- [~Shruthi M R] are you able to respond to Mexina's comment here? > Report categories are inconsistent and causing reports to go missing in the > drop-down > - > > Key: FINERACT-536 > URL: https://issues.apache.org/jira/browse/FINERACT-536 > Project: Apache Fineract > Issue Type: Improvement > Components: System >Affects Versions: 1.0.0 >Reporter: thynn win >Assignee: Markus Geiss >Priority: Minor > Labels: gci, gsoc, p1 > Fix For: 1.3.0 > > Attachments: Untitled.gif > > > Currently in Mifos, if you go to Reports menu and use the drop down to see > "Clients" or "Loans", we notice that some reports are not showing up in the > proper list. > For instance, if you pick Reports>Clients , some client reports such as > "Client Listing" will not show up. This is because the category is 'Clients' > while the expected category value for "Clients" drop down is "Client". > The same issue presents for other category such as Loans. In this case, some > loan reports are created with category "Loan" not "Loans" and then they are > not showing up. It's confusing to end users. > To solve this, review all the report categories and make sure they are > consistent with the expected value from the drop down (be it Client or > Loans). > Acceptance criteria: > All the report categories are cleaned up and consistent and they should all > show up under right drop-down. > The end result is a sql script for the next release that fixes it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-547) Indian Currency Symbol and other currency symbols are wrong
[ https://issues.apache.org/jira/browse/FINERACT-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711874#comment-16711874 ] Edward Cable commented on FINERACT-547: --- [~luckyman000786] Can you include screenshots or examples of this? Can you create a ticket for this on GCI - seems like a good bug to get fixed there. > Indian Currency Symbol and other currency symbols are wrong > --- > > Key: FINERACT-547 > URL: https://issues.apache.org/jira/browse/FINERACT-547 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Reporter: Chirag Gupta >Assignee: Markus Geiss >Priority: Major > Labels: gci, important, p1 > Fix For: 1.3.0 > > > Currently, Indian Currency Symbol and other currency symbols are wrong and > they should be fixed. Fixing this will improve User Experience. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-580) Dashboard summary
[ https://issues.apache.org/jira/browse/FINERACT-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-580: -- Fix Version/s: (was: 1.3.0) 1.4.0 > Dashboard summary > - > > Key: FINERACT-580 > URL: https://issues.apache.org/jira/browse/FINERACT-580 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: sangamesh >Assignee: Markus Geiss >Priority: Major > Labels: gci, gsoc, p1 > Fix For: 1.4.0 > > > Dashboard summary- Dashboard is not working as expected it doesn't show's up > the values. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-580) Dashboard summary
[ https://issues.apache.org/jira/browse/FINERACT-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711869#comment-16711869 ] Edward Cable commented on FINERACT-580: --- [~nksangamesh] Can you provide more details about the dashboard values not being correct? > Dashboard summary > - > > Key: FINERACT-580 > URL: https://issues.apache.org/jira/browse/FINERACT-580 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: sangamesh >Assignee: Markus Geiss >Priority: Major > Labels: gci, gsoc, p1 > Fix For: 1.4.0 > > > Dashboard summary- Dashboard is not working as expected it doesn't show's up > the values. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-589) Searching for groups while creating center is displaying groups which are already member of other center
[ https://issues.apache.org/jira/browse/FINERACT-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable reassigned FINERACT-589: - Assignee: (was: Markus Geiss) > Searching for groups while creating center is displaying groups which are > already member of other center > > > Key: FINERACT-589 > URL: https://issues.apache.org/jira/browse/FINERACT-589 > Project: Apache Fineract > Issue Type: Bug > Components: Groups >Affects Versions: 1.2.0 >Reporter: Santosh Math >Priority: Major > Labels: Volunteer, gci, gsoc, p1 > Fix For: 1.3.0 > > > Go to centers and create a center. While creating center search for existing > groups and select the group which is already part of other center. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-589) Searching for groups while creating center is displaying groups which are already member of other center
[ https://issues.apache.org/jira/browse/FINERACT-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-589: -- Labels: Volunteer gci gsoc p1 (was: gci gsoc p1) > Searching for groups while creating center is displaying groups which are > already member of other center > > > Key: FINERACT-589 > URL: https://issues.apache.org/jira/browse/FINERACT-589 > Project: Apache Fineract > Issue Type: Bug > Components: Groups >Affects Versions: 1.2.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gci, gsoc, p1 > Fix For: 1.3.0 > > > Go to centers and create a center. While creating center search for existing > groups and select the group which is already part of other center. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-589) Searching for groups while creating center is displaying groups which are already member of other center
[ https://issues.apache.org/jira/browse/FINERACT-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711865#comment-16711865 ] Edward Cable commented on FINERACT-589: --- [~santoshmath] Markus is primarily focused on Fineract CN so I don't think he'll be doing any work on this. > Searching for groups while creating center is displaying groups which are > already member of other center > > > Key: FINERACT-589 > URL: https://issues.apache.org/jira/browse/FINERACT-589 > Project: Apache Fineract > Issue Type: Bug > Components: Groups >Affects Versions: 1.2.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, gci, gsoc, p1 > Fix For: 1.3.0 > > > Go to centers and create a center. While creating center search for existing > groups and select the group which is already part of other center. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-597) mifos -- splitting savings into member and donor(sponsor) for a single saving stream
[ https://issues.apache.org/jira/browse/FINERACT-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-597: -- Fix Version/s: (was: 1.3.0) 1.4.0 > mifos -- splitting savings into member and donor(sponsor) for a single saving > stream > > > Key: FINERACT-597 > URL: https://issues.apache.org/jira/browse/FINERACT-597 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.0.0 > Environment: software(cloud) >Reporter: Simon Peter Mulima >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > Fix For: 1.4.0 > > > Hello it would be good to split accounts(saving stream) within an > individual's saving account such that u can separate saving money streams > from for example ( if parents were contributing for their child) a father , > mother and the child *OR* if an individual is receiving topup contributions > from an association which are dependent on themselves making a saving( the > association will give you a saving only if u also contribute and it is > necessary to show what each party has contributed) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-597) mifos -- splitting savings into member and donor(sponsor) for a single saving stream
[ https://issues.apache.org/jira/browse/FINERACT-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711863#comment-16711863 ] Edward Cable commented on FINERACT-597: --- Tagging amounts in savings accounts would be a nice feature. [~simo] can you provide more requirements on how you would like this to work. > mifos -- splitting savings into member and donor(sponsor) for a single saving > stream > > > Key: FINERACT-597 > URL: https://issues.apache.org/jira/browse/FINERACT-597 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.0.0 > Environment: software(cloud) >Reporter: Simon Peter Mulima >Assignee: Markus Geiss >Priority: Major > Labels: gsoc, p2 > Fix For: 1.4.0 > > > Hello it would be good to split accounts(saving stream) within an > individual's saving account such that u can separate saving money streams > from for example ( if parents were contributing for their child) a father , > mother and the child *OR* if an individual is receiving topup contributions > from an association which are dependent on themselves making a saving( the > association will give you a saving only if u also contribute and it is > necessary to show what each party has contributed) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-600) Advanced Accounting Rule
[ https://issues.apache.org/jira/browse/FINERACT-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-600: -- Labels: Volunteer p2 (was: p2) > Advanced Accounting Rule > > > Key: FINERACT-600 > URL: https://issues.apache.org/jira/browse/FINERACT-600 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Loan >Affects Versions: 1.1.0 >Reporter: Nang Hkam >Assignee: Markus Geiss >Priority: Major > Labels: Volunteer, p2 > Fix For: 1.3.0 > > Attachments: image-2018-02-06-16-52-56-083.png > > > There is an issue in Advanced Accounting Rule. > In the loan product setting, two charges (e.g., Servie charge and Loan Fees) > are applied. One of the charges is linked to Accounts Payable (by using > Advanced Accounting Rule). > When we run Balance Sheet/Trial Balance, the amount doesn't show up in the > respective COA (Accounts Payable). But, the expected amount is showing in > other COA (which is Fee Income in my example). > !image-2018-02-06-16-52-56-083.png! > > This is loan product setting : > [https://demo.openmf.org/#/viewloanproduct/673] > > Below is Loan Fees : > [https://demo.openmf.org/#/viewcharge/266] > > Below is Service Charge : > [https://demo.openmf.org/#/viewcharge/265] > [|https://demo.openmf.org/#/viewcharge/266] > [|https://demo.openmf.org/#/viewloanproduct/673] > Below is disbursed loan account: > [https://demo.openmf.org/#/viewloanaccount/2237] > > Below is Trial Balance report > !w9GXoyr9HS7AgBJRU5ErkJggg==|id=img301725! > [|https://demo.openmf.org/#/viewloanaccount/2237] > According to the product setting, Fee Income should be only 2000 credited. > Another 2000 should be credited to Accounts Payable. > > [|https://demo.openmf.org/#/viewloanproduct/673] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-614) Creation of sub rates
[ https://issues.apache.org/jira/browse/FINERACT-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711859#comment-16711859 ] Edward Cable commented on FINERACT-614: --- [~angelboxes] Can we get an update on this - can we target 1.3 or 1.4 for shipping this? > Creation of sub rates > - > > Key: FINERACT-614 > URL: https://issues.apache.org/jira/browse/FINERACT-614 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.1.0 >Reporter: Angel Cajas >Priority: Minor > Labels: p2 > Fix For: 1.3.0 > > > Nominal interest rate for loans can be composed of previously defined > interest rates, When a new loan product or loan account is created you can > choose which rates should apply for the loan. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-616) Apply Penalty for loans scheduler job not running automatically; only running by manually.
[ https://issues.apache.org/jira/browse/FINERACT-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711857#comment-16711857 ] Edward Cable commented on FINERACT-616: --- [~Shruthi M R] Have we made an estimate on this? > Apply Penalty for loans scheduler job not running automatically; only > running by manually. > -- > > Key: FINERACT-616 > URL: https://issues.apache.org/jira/browse/FINERACT-616 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Critical > Labels: gsoc, p1 > Fix For: 1.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-641) Withdrawal fee support for overdrawing account
[ https://issues.apache.org/jira/browse/FINERACT-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-641: -- Labels: Volunteer gsoc p1 (was: gsoc p1) > Withdrawal fee support for overdrawing account > --- > > Key: FINERACT-641 > URL: https://issues.apache.org/jira/browse/FINERACT-641 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Major > Labels: Volunteer, gsoc, p1 > Fix For: 1.3.0 > > > Currently, Savings Withdrawal fee only applicable if withdrawal is done when > balance is greater than zero. > If try to overdraw from savings account, withdrawal fee won't support and > it's throwing the error. > Expected: Withdrawal fee should support overdrawn account . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-626) MOVING CASH FROM HEAD OFFICE ACCOUNTS TO BRANCHES ACCOUNTS IN MIFOS X 17.07.01
[ https://issues.apache.org/jira/browse/FINERACT-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-626: -- Fix Version/s: (was: 1.3.0) 1.4.0 > MOVING CASH FROM HEAD OFFICE ACCOUNTS TO BRANCHES ACCOUNTS IN MIFOS X 17.07.01 > -- > > Key: FINERACT-626 > URL: https://issues.apache.org/jira/browse/FINERACT-626 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization, System >Affects Versions: 1.1.0 >Reporter: Jimmy Jubha Mayala >Priority: Major > Labels: gsoc, p2 > Fix For: 1.4.0 > > > We need a feature in Fineract to enhance cash distribution from head office > to branches, for examplE, in our office we have taken a loan from bank and we > want it be distributed into our branches, we are able to inject this loan > into Head office accounts, but how is it going to be sent to branches > accounts? this is where we got stuck since mifos x 17.07.01 we are using does > not have this feature. > We do request any developer to pick this task. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-626) MOVING CASH FROM HEAD OFFICE ACCOUNTS TO BRANCHES ACCOUNTS IN MIFOS X 17.07.01
[ https://issues.apache.org/jira/browse/FINERACT-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711491#comment-16711491 ] Edward Cable commented on FINERACT-626: --- [~jimmy jubha] Can you please work with [~santoshmath] to share more requirements of what you need to support. > MOVING CASH FROM HEAD OFFICE ACCOUNTS TO BRANCHES ACCOUNTS IN MIFOS X 17.07.01 > -- > > Key: FINERACT-626 > URL: https://issues.apache.org/jira/browse/FINERACT-626 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization, System >Affects Versions: 1.1.0 >Reporter: Jimmy Jubha Mayala >Priority: Major > Labels: gsoc, p2 > Fix For: 1.3.0 > > > We need a feature in Fineract to enhance cash distribution from head office > to branches, for examplE, in our office we have taken a loan from bank and we > want it be distributed into our branches, we are able to inject this loan > into Head office accounts, but how is it going to be sent to branches > accounts? this is where we got stuck since mifos x 17.07.01 we are using does > not have this feature. > We do request any developer to pick this task. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-633) New Penalty Charge not appearing in Product dropdown list
[ https://issues.apache.org/jira/browse/FINERACT-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711487#comment-16711487 ] Edward Cable commented on FINERACT-633: --- [~sifiso] I think [~santoshmath] this is not a bug but rather a feature request/enhancement. Are you able to complete and share this with community? For now, i'm moving this to 1.4.0 release. > New Penalty Charge not appearing in Product dropdown list > - > > Key: FINERACT-633 > URL: https://issues.apache.org/jira/browse/FINERACT-633 > Project: Apache Fineract > Issue Type: Bug > Components: Charges, Loan >Affects Versions: 1.1.0 > Environment: v18.03.01 >Reporter: Sifiso Mtetwa >Priority: Minor > Labels: easyfix, gsoc, p1 > Fix For: 1.3.0 > > > We have been developing a new feature for penalties overdue on maturity > [https://mifosforge.jira.com/browse/MIFOSX-2848?filter=-2] We have an issue > where after you create the penalty in the charges area with a new charge time > type of overdue on maturity and submit it, it does not appear in loan > products penalties dropdown box for selection. Wanted to find out which class > fetches the penalties that are fetched to appear in this list yet in table > m_charges it appears fine. We have added some code in the UI to fetch the > required variables but it still does not appear. We can’t proceed beyond this > point. Please advise -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-638) Creation of API's for Web App and Self Service Admin Portal
[ https://issues.apache.org/jira/browse/FINERACT-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711486#comment-16711486 ] Edward Cable commented on FINERACT-638: --- [~Shruthi M R] Where do we stand with implementation of these APIs? > Creation of API's for Web App and Self Service Admin Portal > --- > > Key: FINERACT-638 > URL: https://issues.apache.org/jira/browse/FINERACT-638 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization, System, User Management >Reporter: Abhay Chawla >Assignee: Shruthi M R >Priority: Major > Labels: gsoc, p1 > Fix For: 1.3.0 > > > List of API's that will be required are as follows- > App Configuration for the new web app, based on the Tenant so that they can > be accessed on the login page itself before authentication: > 1) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format > 2) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name > 3) Support for saving and retrieving Default theme and font to be used within > the application > 4) Support for saving and retrieving contact information including website, > email, contact no (multiple if required) > App Configuration for the self-service mobile app and online banking app, > based on Tenant so that they can be accessed on the login page itself before > authentication: > 5) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format (common) > 6) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name (common and will be used as > required by whichever application) > 7) Support for saving and retrieving Default theme and font to be used within > the application (separate for mobile and online banking app) > 8) Support for saving and retrieving contact information including website, > email, contact no (common, multiple if required) > Self Service User Management and Creation > 1) Support for viewing current and potential self-service users. > 2) Support for activating and deactivating self-service users (single and > bulk). > 3) Support for creating new self-service users. > 4) Support for viewing, editing and changing the password of a self-service > user. > Refer to Issues: > https://github.com/openMF/web-app/issues/33 > https://github.com/openMF/web-app/issues/34 > https://github.com/openMF/web-app/issues/35 > https://github.com/openMF/web-app/issues/36 > Self Service JIRA Link: > https://mifosforge.jira.com/wiki/spaces/MIFOSX/pages/102629583/Customer+Self+Service -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-643) Journal Entries are not filterable by type of entry: system
[ https://issues.apache.org/jira/browse/FINERACT-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-643: -- Labels: Volunteer gci gsoc p1 (was: gci gsoc p1) > Journal Entries are not filterable by type of entry: system > --- > > Key: FINERACT-643 > URL: https://issues.apache.org/jira/browse/FINERACT-643 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Major > Labels: Volunteer, gci, gsoc, p1 > Fix For: 1.3.0 > > > Related Front -End Issue: > https://github.com/openMF/web-app/issues/236 > As a developer, I am unable to implement the filter for Journal Entries by > type of entry: system, as the only parameter available to filter entries by > type is manualEntriesOnly which filters manual entries (as clear from its > name). There is no way to filter system entries from server-side. > (similar issue in community-app) > Due to a large number of entries in database (over 8), its essential to > implement it from server-side because the default implementation of sending a > HTTP request to get all the entries at once and implementing the logic on > client-side will be too costly for people with slow internet connections. > > Refer: [https://demo.openmf.org/api-docs/apiLive.htm#journalentries_list] > Expected Behaviour: > Journal Entries should be filterable by type of entry: system apart from the > manual as well from the server-side so that it can be implemented on the > client side. > h2. Actual Behaviour > Journal Entries are not filterable by type of entry: system from the > server-side due to which filter by type of entry cannot be implemented > properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-643) Journal Entries are not filterable by type of entry: system
[ https://issues.apache.org/jira/browse/FINERACT-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-643: -- Labels: gci gsoc p1 (was: gsoc p1) > Journal Entries are not filterable by type of entry: system > --- > > Key: FINERACT-643 > URL: https://issues.apache.org/jira/browse/FINERACT-643 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Major > Labels: gci, gsoc, p1 > Fix For: 1.3.0 > > > Related Front -End Issue: > https://github.com/openMF/web-app/issues/236 > As a developer, I am unable to implement the filter for Journal Entries by > type of entry: system, as the only parameter available to filter entries by > type is manualEntriesOnly which filters manual entries (as clear from its > name). There is no way to filter system entries from server-side. > (similar issue in community-app) > Due to a large number of entries in database (over 8), its essential to > implement it from server-side because the default implementation of sending a > HTTP request to get all the entries at once and implementing the logic on > client-side will be too costly for people with slow internet connections. > > Refer: [https://demo.openmf.org/api-docs/apiLive.htm#journalentries_list] > Expected Behaviour: > Journal Entries should be filterable by type of entry: system apart from the > manual as well from the server-side so that it can be implemented on the > client side. > h2. Actual Behaviour > Journal Entries are not filterable by type of entry: system from the > server-side due to which filter by type of entry cannot be implemented > properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-647) Allow rescheduling of loan with recalculation of interest enabled
[ https://issues.apache.org/jira/browse/FINERACT-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711482#comment-16711482 ] Edward Cable commented on FINERACT-647: --- [~Shruthi M R] Have we estimated the level of effort for this issue? > Allow rescheduling of loan with recalculation of interest enabled > - > > Key: FINERACT-647 > URL: https://issues.apache.org/jira/browse/FINERACT-647 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.1.0 >Reporter: Mexina Daniel >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > There is a need of allowing the loan which has enabled interest recalculation > to be rescheduled once needed. > for now the system does not allow that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
