[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 ] Santosh Math updated FINERACT-12: - Fix Version/s: 1.3.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: p1 > Fix For: 1.3.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-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 ] Santosh Math updated FINERACT-99: - Fix Version/s: 1.3.0 > 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] [Updated] (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:all-tabpanel ] Santosh Math updated FINERACT-26: - Fix Version/s: 1.3.0 > 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: 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-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 ] Santosh Math updated FINERACT-13: - Fix Version/s: 1.3.0 > 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: 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-270) Unable to waive all Loan charges
[ https://issues.apache.org/jira/browse/FINERACT-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-270: -- Fix Version/s: 1.3.0 > 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.3.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] [Updated] (FINERACT-186) optimising the Post Interest For Savings batch job using pagination
[ https://issues.apache.org/jira/browse/FINERACT-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-186: -- Fix Version/s: 1.3.0 > optimising the Post Interest For Savings batch job using pagination > --- > > Key: FINERACT-186 > URL: https://issues.apache.org/jira/browse/FINERACT-186 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: venkat Ganesh >Assignee: Markus Geiss >Priority: Minor > Labels: p1 > Fix For: 1.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Santosh Math updated FINERACT-146: -- Fix Version/s: 1.3.0 > 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-274) Not able to create the same datatable which was rejected by the maker checker before
[ https://issues.apache.org/jira/browse/FINERACT-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-274: -- Fix Version/s: 1.3.0 > Not able to create the same datatable which was rejected by the maker checker > before > > > Key: FINERACT-274 > URL: https://issues.apache.org/jira/browse/FINERACT-274 > Project: Apache Fineract > Issue Type: Bug > Components: Data Tables >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: confirm, p1 > Fix For: 1.3.0 > > > Posted by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1246 > Original Description: > 1. Click on Admin ->System - enable maker-checker. > 2. Click on Admin ->System - Configure maker-checker tasks -> select check > box for create, update and delete data tables. > 3. Click on the Admin -> System -> Manage data tables -> Create data table - > and create data table for client. > 4. The navigated page displays "Waiting For Checker Approval" -> Click on > details -> Click on reject button in "View Checker Inbox" -> click on confirm > in confirmation page. > With the above action in UI the data table will not appear, but in the > database the table is still exist. > > Again try to create datable with the same name as above, which displays > > error message as the data table already exists, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-276: -- Fix Version/s: 1.3.0 > 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-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 ] Santosh Math updated FINERACT-271: -- Fix Version/s: 1.3.0 > 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] [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 ] Santosh Math updated FINERACT-281: -- Fix Version/s: 1.3.0 > 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: 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-284) Collection Sheet as a tool for collecting savings
[ https://issues.apache.org/jira/browse/FINERACT-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-284: -- Fix Version/s: 1.3.0 > 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: 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] [Updated] (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:all-tabpanel ] Santosh Math updated FINERACT-307: -- Fix Version/s: 1.3.0 > 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] [Updated] (FINERACT-285) For Savings account Deposits and Withdrawals are not working if the "Start interest calculation date" is defined
[ https://issues.apache.org/jira/browse/FINERACT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-285: -- Fix Version/s: 1.3.0 > For Savings account Deposits and Withdrawals are not working if the "Start > interest calculation date" is defined > - > > Key: FINERACT-285 > URL: https://issues.apache.org/jira/browse/FINERACT-285 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > Labels: confirm, p1 > Fix For: 1.3.0 > > Attachments: scr1.png, scr2.jpeg > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1560 > Original Description: > 1. Create a Savings product and assign it to a client on 01 July 2014 -> > Approve and activate the account on same date. > 2. In Database - m_savings_account table enter date as 10 August 2014 in > start_interest_calculation_date column for the same account. > > After attaching the start interest calculation date application is not > > allowing to do any deposits and withdrawals (before and after start > > interest calculation date) displayed error message as "Savings account > > transaction incorrect start interest calculation date". -- 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 ] Santosh Math updated FINERACT-348: -- Fix Version/s: 1.3.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: p1 > Fix For: 1.3.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-314) If Tranche disbursement charge payment mode is Account transfer then after first disbursement the charge collection is improper
[ https://issues.apache.org/jira/browse/FINERACT-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-314: -- Fix Version/s: 1.3.0 > If Tranche disbursement charge payment mode is Account transfer then after > first disbursement the charge collection is improper > --- > > Key: FINERACT-314 > URL: https://issues.apache.org/jira/browse/FINERACT-314 > Project: Apache Fineract > Issue Type: Bug > Components: Charges >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Minor > Labels: p1 > Fix For: 1.3.0 > > Attachments: 91.png, 93.png > > > Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2194 > Original Description: > 1. Create Tranche disbursement charge with Charge Payment Mode as Account > transfer. > 2. Create Tranche loan product with 2 tranches and above created charge > attached > 3. Create Savings product and create a client with active savings product > above created. > 4. For the same above client submit new loan application with the above > savings account and Tranche disbursement charge attached while submitting the > application, tranche attached on 01 August 2015 and amount is 5000, 2nd > tranche on 01 September 2015 and amount is 5000 -> Approve and disburse the > first tranche on 01 August 2015. > > In Summary page displaying as both tranche disbursement charges as due > > In Repayment schedule is displaying properly > > In Transactions page and In Charges page both Tranche disbursement charges > > are displaying as collected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Santosh Math updated FINERACT-336: -- Fix Version/s: 1.3.0 > 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: 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-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:all-tabpanel ] Santosh Math updated FINERACT-363: -- Fix Version/s: 1.3.0 > 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] [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: 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 > 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 ] Santosh Math updated FINERACT-463: -- Fix Version/s: 1.3.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: gsoc2017, p1 > Fix For: 1.3.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-416) Interest to be calculated for the whole loan term given
[ https://issues.apache.org/jira/browse/FINERACT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-416: -- Fix Version/s: 1.3.0 > Interest to be calculated for the whole loan term given > --- > > Key: FINERACT-416 > URL: https://issues.apache.org/jira/browse/FINERACT-416 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Mexina Daniel >Assignee: Markus Geiss >Priority: Critical > Labels: gsoc2017, p1 > Fix For: 1.3.0 > > > As for some of the MFI practise here in our country, they specify the > interest for the whole loan term given, i.e their loan product have the > interest for the whole loan term regardless of the frequency of repayment () > To accomplish this in mifos, a user has to do calculation of finding an > interest of a month/year with respect of the loan term of that specific > client. This is a very tiresome work as for a day a user can have apply many > loans and the task of calculation make the work even harder. > I was suggesting improvement in the loan product, to be able to allow the > interest rate of the whole loan term. > Example: > Loan product - Development Loan > Amount - Min: 100,000, Max:1,000,000 > Interest - 20% > Loan term - From 3months to 6months > -- This means the interest given is for any loan term the client will want to > take the loan. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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 ] Santosh Math updated FINERACT-504: -- Affects Version/s: 1.0.0 Fix Version/s: 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: 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-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: -- Fix Version/s: 1.3.0 > 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: gsoc2017, 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] [Updated] (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:all-tabpanel ] Santosh Math updated FINERACT-478: -- Affects Version/s: 1.0.0 Fix Version/s: 1.3.0 > 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: gsoc2017, 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-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 ] Santosh Math updated FINERACT-505: -- Affects Version/s: 1.0.0 Fix Version/s: 1.3.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: p1 > Fix For: 1.3.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 ] Santosh Math updated FINERACT-513: -- Affects Version/s: (was: 1.1.0) Fix Version/s: (was: 1.1.0) (was: 1.0.0) 1.3.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: 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-528) After taking survey for a client, Survey is displaying score of each question in stead of total score of each survey
[ https://issues.apache.org/jira/browse/FINERACT-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-528: -- Fix Version/s: (was: 1.1.0) 1.3.0 > After taking survey for a client, Survey is displaying score of each question > in stead of total score of each survey > > > Key: FINERACT-528 > URL: https://issues.apache.org/jira/browse/FINERACT-528 > Project: Apache Fineract > Issue Type: Improvement > Components: Client, Surveys >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > -- 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 ] Santosh Math updated FINERACT-518: -- Fix Version/s: 1.3.0 > 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: 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-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:all-tabpanel ] Santosh Math updated FINERACT-536: -- Fix Version/s: (was: 1.1.0) 1.3.0 > 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: 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] [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 ] Santosh Math updated FINERACT-535: -- Fix Version/s: 1.3.0 > 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, 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] [Updated] (FINERACT-546) Cannot remove Group from Center
[ https://issues.apache.org/jira/browse/FINERACT-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-546: -- Fix Version/s: 1.3.0 > Cannot remove Group from Center > --- > > Key: FINERACT-546 > URL: https://issues.apache.org/jira/browse/FINERACT-546 > Project: Apache Fineract > Issue Type: Bug > Components: Groups >Reporter: May Myint >Assignee: Shaik Nazeer Hussain >Priority: Major > Labels: gci2017, group, p1 > Fix For: 1.3.0 > > > Unable to remove Group from Center. > Error message "field is required. error.msg.group.not.in.center" > https://demo.openmf.org/#/viewcenter/1175 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Santosh Math updated FINERACT-547: -- Fix Version/s: 1.3.0 > 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: 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-561) We are not able disable 'Financial-Year-Beginning-Month' in Global configuration of Mifos
[ https://issues.apache.org/jira/browse/FINERACT-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-561: -- Fix Version/s: 1.3.0 > We are not able disable 'Financial-Year-Beginning-Month' in Global > configuration of Mifos > -- > > Key: FINERACT-561 > URL: https://issues.apache.org/jira/browse/FINERACT-561 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > Go to Admin>system>configuration. Search for > 'Financial-Year-Beginning-Month' and disable it. > Create an FD product (or any saving product). and activate it in such > way that financial year end is in between the period of FD. > Interest is getting posted at the end of financial year to the savings > account. -- 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 ] Santosh Math updated FINERACT-580: -- Affects Version/s: 1.2.0 Fix Version/s: 1.3.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.3.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] [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 ] Santosh Math updated FINERACT-589: -- Affects Version/s: 1.2.0 Fix Version/s: 1.3.0 > 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: 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-602) Unable to Submit loan application in demo server, going in infinite loop
[ https://issues.apache.org/jira/browse/FINERACT-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Cable updated FINERACT-602: -- Fix Version/s: 1.2.0 > Unable to Submit loan application in demo server, going in infinite loop > > > Key: FINERACT-602 > URL: https://issues.apache.org/jira/browse/FINERACT-602 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Myrle Krantz >Priority: Blocker > Labels: p1 > Fix For: 1.2.0 > > > For the following client: > [https://demo.openmf.org/#/viewclient/4513] > Try to submit loan (clicking on 'New Loan) > Provide 'Submitted Date' and 'Expected Disbursement Date' as 11th February > 2018 -- 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 ] Santosh Math updated FINERACT-600: -- Labels: p2 (was: ) > Advanced Accounting Rule > > > Key: FINERACT-600 > URL: https://issues.apache.org/jira/browse/FINERACT-600 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Loan >Reporter: Nang Hkam >Assignee: Markus Geiss >Priority: Major > Labels: p2 > 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] [Updated] (FINERACT-602) Unable to Submit loan application in demo server, going in infinite loop
[ https://issues.apache.org/jira/browse/FINERACT-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-602: -- Labels: p1 (was: ) Component/s: Loan > Unable to Submit loan application in demo server, going in infinite loop > > > Key: FINERACT-602 > URL: https://issues.apache.org/jira/browse/FINERACT-602 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Myrle Krantz >Priority: Blocker > Labels: p1 > > For the following client: > [https://demo.openmf.org/#/viewclient/4513] > Try to submit loan (clicking on 'New Loan) > Provide 'Submitted Date' and 'Expected Disbursement Date' as 11th February > 2018 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-8) Web UI for Microfinance Institutions Practicing Group Lending
Edward Cable created FINCN-8: Summary: Web UI for Microfinance Institutions Practicing Group Lending Key: FINCN-8 URL: https://issues.apache.org/jira/browse/FINCN-8 Project: Fineract Cloud Native Issue Type: New Feature Reporter: Edward Cable While the current Mifos X stack caters to one operational methodology and has one distinct user interface and navigational flow, Fineract CN and it's broader applicability enables many different operational workflows to be supported and will have different flavors of the web UI. For the brand new Apache Fineract CN architecture, the web UI for the first use cases has been built out to support a teller-driven credit union operational methodology. The user interface and navigational flows for such an operational model is very different from that of a microfinance institutinon with group and center-based operations whereby the loan officer travels out to the customers rather than the customer goes to the branch office. The UI that will be built out for this project will be very similar to the UI that was found in the current Gen 2 Mifos X web app as well as the original Gen 1 web app with support for viewing group and center hierachies, having a different drilldown navigational flow, etc. A number of these UI elements will still need the requisite support on the back-end. Intern will implement the front-end UI screens for the Fineract CN web UI for the following functionalities and use case: * Center & Group Creation * Center Summary and Details Page * Group Summary and Details Page * Group/Center Meeting Page * Group, Center Listing View * Drilldown navigation via Groups/Centers * Collection sheet user interface * Transferring clients between groups * Group loan creation UI * Group loan UI -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-7) Fineract CN Mobile 2.0
Edward Cable created FINCN-7: Summary: Fineract CN Mobile 2.0 Key: FINCN-7 URL: https://issues.apache.org/jira/browse/FINCN-7 Project: Fineract Cloud Native Issue Type: Improvement Reporter: Edward Cable Epic-level issue to house issues and stories related to developing Version 2.0 of Fineract CN Mobile. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-6) Fineract CN REST API Documentation
Edward Cable created FINCN-6: Summary: Fineract CN REST API Documentation Key: FINCN-6 URL: https://issues.apache.org/jira/browse/FINCN-6 Project: Fineract Cloud Native Issue Type: New Feature Reporter: Edward Cable Our newest generation architecture, Apache Fineract CN has a set of REST APIs that are not documented yet. Given that the architecture is microservices-based, Spring REST Docs will be the chosen tool of choice to overcome limitations of static documentation: # Live documentation that is accurate, based on Test-driven development and does not need to be maintained manually in parallel to the source code which actually defines the REST API, and therefore can stay in sync # It will be live and you won't have to set up a REST tool such as e.g. [Postman|https://www.getpostman.com/] ; Co. to "explore" it. The goal of this project is address this by using _[Spring REST Docs|http://projects.spring.io/spring-restdocs/]__;_ # Spring MVC Test : [https://docs.spring.io/spring/docs/current/spring-framework-reference/testing.html] # Spring REST Docs : [https://spring.io/guides/gs/testing-restdocs/] # Asciidoctor : [http://asciidoctor.org/] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
