 |
 |
 |
 |
|||
 |
||||||
| Updates of version 7.10, 7.09, 7.08, 7.07, 7.06, 7.05, 7.04, 7.03, 7.02, 7.01,7.00 | ||
| Updates of all versions are available through the above links. Crystal Clear is committed to making Loan Performer the best software for Microfinance institutions around the globe. | ||
| 7.01 | to top  |
|
| 1. Corrected: the creation of a corporate database was not possible in version 7.00. 2. Corrected: the table Exchange.dbf had a field called "Start". This is a field name that is not allowed in SQL Server. 3. Corrected: if user selected SQL Server at login but had no SQL ODBC database defined, he would get all kinds of errors. 4. Corrected: in earlier versions user could click on a header on any item under Support Files and everything would be ordered to number or label. In version 7.00 you couldn't do this anymore. to top 5. Corrected: the item Configuration/User access rights has been organised in such a way that menu items that belong together show up together and show up in the same color. If user clicks on the first column items are organised alphabetically. Clicking as second time restores the original position. The Guest column has been made modifiable so that users can limit access for the guest user (ACME, Haiti). 6. Corrected: if user modified an individual client, saved and continued with another client, sometimes an error could occur (Error number 1234, Subscript is outside defined range, Mukono Teachers Sacco, Uganda). to top 7. Corrected: if user entered an individual client, a group or business, saves but closed the payment of registration fees window by clicking the 'x' in the right top, then selected again menu Clients/Groups to add another client, an error was generated ("Cannot access table" in case of ind client, "Unknown member OMemRepay" in case of a group or business client). 8. Corrected: if user had created a folder for signature files and indicated this at Configuration/General, the button for signature files at Ind Clients and Groups did not open with this folder. Now Loan Performer creates 2 sub-folders at installation: Photo and Signature and defaults the images at entry of clients to these directories. to top 9. Corrected: if a client was entered with a specific client category (only client category 1), it was possible that at modification of the client data, the elements of this category were mixed up (Socodevi, DR Congo). 10. Corrected: if user updated group member data and the end of membership was not empty, (s)he would get an error (Wrong function type, argument, Buusaa Gonofaa, Ethiopia). Corrected: once a savings account was closed, it could not be opened again as the "Closing Date" textbox became read-only (Horizonti, Macedonia). 11. Corrected: the printout of the second page of the Report on Clients listens to the preview/print selection of the first page (and not of the second page). to top 12. Corrected: user could enter a second transaction of buying of shares on the same day and time as the previous one. This should not have been possible as it is ambiguous which transaction came first. 13. Corrected: if the original transaction was a payment of shares from one of the savings accounts of the client, the modification of a shares transaction did not show the mode of payment as it was originally (Socodevi, DR Congo). 14. Corrected: if a client bought a share from the savings account and later on the user wanted to modify the transaction date and went to menu Shares/Modify transaction and changed the date, the original transaction was still on the savings account plus the new transaction. to top 15. Corrected: if user defined several different cash accounts and then modified a shares transaction by changing the cash account, Loan Performer did not book both debit and credit. 16. Corrected: if the user made a mistake and entered an incorrect number of shares that were paid from the client's savings account and went into Shares/Modify Transaction and changed the number of shares, the original transaction was not deleted from the savings account (Socodevi, DR Congo). 17. Corrected: the minimum balance for a savings account was not respected even though it was configured that way (Gamstar, Gambia). to top 18. Corrected: when a savings account is closed, a closing fee was automatically booked and deducted from the outstanding balance of the client. Afterwards the user could withdraw the whole remaining balance, even the minimum balance. However in recent versions, the withdrawal beyond the minimum balance was no longer possible (Gamstar, Gambia). 19. Corrected: if you transferred a member from one group to another and savings are tracked at group member level, Loan Performer did not post the balance of the group member's savings account from the old group to the new group (KWFT, Kenya). 20. Corrected: user could not modify savings rewards and charges when the booking of transactions to the general ledger was activated. to top 21. Corrected: the report on Modified Savings Transactions showed an incorrect Balance amount (if user had entered 1,000 as a single deposit, then changed it to 300, the Balance column was still showing 1,000, Labalu, Kenya). 22. Corrected: the interest calculation for savings on monthly minimum balances did not show any individual accounts (Mikrobank, Papua New Guinea). 23. Corrected: the Group Member Savers Statement could not be printed for a period in which the member had no transactions even if there was a balance brought forward at the start of the period (KWFT, Kenya). 24. Corrected: the Group Members Savings Balances report, order by member name, group name, showed under "Totals" the number of accounts and average. However it already had these. The labels have been removed. to top 25. Corrected: if user has defined a time-deposit and entered a new time-deposit that is created by drawing from the client's savings account, Loan Performer came up with an incorrect validation message that said that the amount, interest or period of the time-deposit did not fall within the pre-set range (Socodevi, DR Congo). 26. Corrected: if user had 2 defined products for time-deposits Loan Performer did not refresh the GL accounts on the 2nd page of Configuration/Time-Deposits if the user choose a second product (Socodevi, DR Congo). to top 27. Corrected: if user had entered a time-deposit with interest to be added to the client's savings account on a monthly basis, (s)he was still able to modify the time-deposit and change the interest calculation to maturity. Now once interest has been calculated, the parameters of the time-deposit cannot change anymore. 28. Corrected: if a time-deposit is to be renewed for another term, it is nowhere to be found in the system. Now Loan Performer closes the old TD and issues a new one. 29. Corrected: if client withdraws a time-deposit, Loan Performer kept the initial amount of the time deposit as part of the current balances in the Savings Balances reports (Gamstar, Gambia). to top 30. Corrected: the pages Configuration/Savings GL accounts and Configuration/Loans GL Accounts showed incorrectly that the Cheque account served for savings and loans. This is not the case as the account on the savings page only serves savings and the one on the loans page only loans (Enterprise Mentors, USA). 31. Corrected: if under system/conf/general, user choose to set default loan type to group loans, Loan Performer created an error ("Field Varvalue does not accept null values"). to top 32. Corrected: the dates for half-monthly installments were incorrectly set on the 15th of the month instead of the 16th (if loan application date was on the first, Enterprise Mentors, USA). 33. Corrected: the interest for loans on declining balance was incorrect in case of daily interest calculation and 360 interest days per year (in this case each month should have 30 days, independent of the real number of days, Enterprise Mentors, USA). to top 34. Corrected: the loan application did not consider a grace period of just 1 day (Enterprise Mentors, USA). 35. Corrected: if user entered a group loan with member tracking enabled and interest deducted at disbursement, the repayment schedule at group level incorrectly showed a principal amount to be paid on the disbursement date and an interest amount due on the first instalment after disbursement. Although the dues for the members were correct. 36. Corrected: if a loan application had commission with every installment, the commission was not visible on the loan repayment schedule and loan ledger card (Forde, Uganda). to top 37. Corrected: when at loan application, user clicked "Check Savings", Loan Performer only showed the group savings and not the group member savings (KWFT, Kenya). 38. Corrected: if user entered a group loan, went to page 3 for the group member repayment schedule, returned to page 2 and modified the due dates, then on page 3 indicated NOT to recalculate the group member repayment schedule, the due dates for the group members were not the same as for the group. to top 39. Corrected: when at loan application, user choose to print (to printer) the repayment schedule, s(he) would get an unrelated question: "Do you want to re-print/re-view the loans received by group members report?". This is also when entering an individual loan. 40. Corrected: if at loan application user modified a guarantor and did not put a middle name, (s)he was not able to save this guarantor (Loan Performer wants a middle name). to top 41. Corrected: if a loan was disbursed to the clients savings account and the client had several different savings products, Loan Performer could disburse this to the wrong savings product (Socodevi, DR Congo). 42. Corrected: the disbursement of loans on declining balance with instalments for interest in the grace period could result in incorrect due amounts and even negative amounts (KWFT, Kenya). to top 43. Corrected: if a loan was disbursed and after the disbursement, the user indicated that the due dates and interest had to be recalculated (option 4), the due amounts no longer respected the setting of the number of decimals in the configuration (Socodevi, DR Congo). 44. Corrected: if a receipt was printed at disbursement and the loan was disbursed to the client's savings account, the receipt indicated incorrectly that the disbursement was in cash (Socodevi, DR Congo). to top 45. Corrected: the report Loan Repayment Schedule at disbursement showed a different method of calculating penalties than at loan application (Socodevi, DR Congo). 46. Corrected: negative balances were produced if two payments were made on the same day for loans on declining balance and the payment date was not a due date (KWFT, Kenya). 47. Corrected: a pre-payment for loans on declining balance with group member tracking enabled and interest recalculated, could lead to negative balances (KWFT, Kenya). 48. Corrected: if a loan was entered with declining balance discounted and interest calculated in days and client paid exactly according to the repayment schedule given at disbursement, Loan Performer calculated different interest amounts at repayment. to top 49. Corrected: if a loan repayment was entered on the first due date for the full balance of principal and interest, then when the repayment was deleted, the dues were not reset to their original value. 50. Corrected: if a loan repayment was entered for a group loan with tracking of member loans enabled and the loan had no interest due, but only commission with every installment and the user entered a pre-repayment, the pre-payment would not be correctly updating the group and member balances (Forde, Uganda). to top 51. Corrected: if user entered a repayment for a loan on declining balance with commission for every instalment on the due date and activated the recalculation of interest, the interest was not included in the amount to repay. If user clicked the Back button, then the Next button and then the Back button again, activated the recalculation of interest and clicked Next, the commission was part of the amounts to pay (Enterprise Mentors, USA). 52. Corrected: if user entered a pre-payment for a loan on declining balance with commission for every instalment, the commission was not taken in the amount repaid (Enterprise Mentors, USA). to top 53. Corrected: if user entered a pre-payment for a loan on declining balance with commission for every instalment and manually put in the commission ("Repayment priorities modifiable" is activated at Configuration/Loans part 1.), the pre-paid commission did not reduce the commission of the next instalment (Enterprise Mentors, USA). 54. Corrected: the repayment of a group loan (the normal menu item) resulted in an error (Variable SQL Column not found, Buusaa Gonofaa, Ethiopia). 55. Corrected: the closing of a loan on declining balance at repayment, caused negative interest balances (KWFT, Kenya). 56. Corrected: if the menu item "Group Member Repayment" was used and the group had loans on both declining balance and flat rate, Loan Performer calculated wrong amounts (KWFT, Kenya). to top 57. Corrected: the report that is printed when loans in arrears are repaid from the savings account, showed an incorrect old savings balance (this was in fact the new balance on the savings account, Socodevi, DR Congo). 58. Corrected: if a user deleted a loan repayment, Loan Performer reversed all transaction in the general ledger with the same transaction code. Sometimes the user could have the same transaction code for different transactions. So the deletion would affect transactions that had nothing to do with the deleted loan repayment. Now Loan Performer also checks on the kind of transaction (in this case defined as a loan repayment) so that it only reverses transactions with the same transaction code and the same transaction type. to top 59. Corrected: the importation of loan applications resulted in an error (Variable 60. Corrected: the importation of loan applications for group loans resulted in an error (Alias 61. Corrected: if user imported repayments with setting "Member gets individual loan" (Grameen lending type), the loan importation module gave an error message (Error: There are some members not found in this Loan! This repayment is therefore not valid!, SPBD, Samoa). to top 62. Corrected: Loan Performer disregarded the grace period when importing loan repayments for group loans (Buusaa Gonofaa, Ethiopia). 63. Corrected: when importing loan repayments with declining balance amortised, user could get error (Variable 'Int' not found). 64. Corrected: if user selected the 2nd menu option under Accounting (Add or Modify Transaction), the transaction code did not increase and user could enter a new transaction with an existing transaction code. 65. Corrected: the write off of several loans automatically, gave an error. 66. Corrected: the report on repayments during a period gave a wrong repayment rate that calculated the repayments of the period against the dues since disbursement. Now the calculation has been modified so that the repayment rate is based on the repayments since disbursement against the dues since disbursement. A note has been added to the report explaining how the repayment rate is calculated (Eclof, Kenya). to top 67. Corrected: the Portfolio at Risk indicators on the Indicators report were showing arrears and not Outstanding Balances of loans in arrears (Eclof, Kenya). 68. Corrected: the column Qualitative Repayment Rate on the Performance Monitoring Indicators report was showing negatives if there were pre-payments in a month. 69. Corrected: the Loan Status Report when printed for all group members showed even members who were no longer part of the group (KWFT, Kenya). 70. Corrected: the Loan Status Report was showing loans on declining balance with pre-payments as being in arrears (KWFT, Kenya). to top 71. Corrected: the Savings balance on the Loan Status report sometimes did not match the balances of the Group Member Savings Balances report (KWFT, Kenya). 72. Corrected: the Loan Status Report could only produce a printout with savings if the checkbox "Print each group on a different page" was de-selected (KWFT, Kenya). 73. Corrected: the Loan Status report if printed for all savings products gave an incorrect total savings amount (KWFT, Kenya). 74. Corrected: the Group Member Arrears report gave different results if printed with non-English date settings (KWFT, Kenya). to top 75. Corrected: the Group Members Performance Monitoring the column 13, No of members not received loans for the current month was incorrect. 76. Corrected: if user incorrectly rescheduled group member principal amount at loan application (loan tracked at group member |
||
| 7.00 | to top |
|
|
1. Corrected: the membership of group members could be ended when they still had savings balances (KWFT, Kenya). 2. Corrected: user was able to import group members with group codes that did not exist (SPBD, Samoa). 3. Corrected: the importation of clients showed the progress with the current record out of a total. However the total was always indicating 0. 4. Corrected: if client had deposited a cheque and the cheque was not cleared, the user was able to transfer the un-cleared part of the savings balance to another client. 5. Corrected: if savings interest was calculated according to monthly minimum balances, the transactions posted on the last day of the month were not taken into consideration when calculating the interest (Mikrobank, Papua New Guinea). 6. Corrected: the savings report "Period Balances" gave an error message ("Too many variables") if the number of records were too much to process. to top 7. Corrected: if user modified a time-deposit and changed the date, the maturity date was not updated. 8. Corrected: if user entered a loan application with interest deducted at disbursement, and disbursed the loan 1 or 2 instalments later than the loan application date, the interest balance in the Due table was incorrect for the 1st and 2nd instalment. 9. Corrected: if user entered a loan application with commission for every instalment for a group loan with member tracking enabled, Loan Performer did not calculate any commission at group member level (Hope International, Sierra Leone). 10. Corrected: if user entered a percentage for commission to be paid with every instalment and group member tracking was enabled, the commission that was calculated for every group member did not depend on the loan amount of the member (Forde, Uganda). to top 11. Corrected: a loan disbursement with interest deducted could not be saved. 12. Corrected: if at loan repayment, user closed a loan, the dues were not reset to the repayment date, causing Loan Performer to report dues while actually they have been repaid (Horizonti, Macedonia). 13. Corrected: if user entered a pre-payment for a group loan where loans are tracked at member level and member gets an individual loan, an error message is produced (Error number 111, Cannot update cursor). to top 14. Corrected: when at loan repayment, user clicked the Back button, the Loan Balance textbox suddenly became zero. 15. Corrected: a wrong validation message is displayed whenever user attempted to repay arrears from saving and no savings balance was available. Loan Performer gave the following message: "All loans accounts have sufficient blocked amount. and the same total for the Members for some loans. These transactions are not possible. Do you want to view them?" 16. Corrected: when loans are imported with interest deducted at disbursement, Loan Performer incorrectly added the interest to the disbursed amount and indicated incorrectly that the loan was not fully repaid when user entered all repayments manually (ARC, Sierra Leone). to top 17. Corrected: when user ordered by Loan Cycle or Categories or Sector etc,..., on the Group Members Arrears Report, each subtotal was always cumulating its own figure + the previous subtotal. (eg: if there are 2 loans for cycle 1 and 5 loans for cycle 2, the subtotal for cycle 2, shows 7 in stead of 5, CIDR, Ethiopia). 18. Corrected: when user ordered by Loan Cycle or Categories or Sector etc,..., on the Group Members Amount Due report, the grand total was only showing the last sub-total (and not adding the previous ones, CIDR, Ethiopia). 19. Corrected: the Loan Cycles report did not include written off loans, thus showing less loans than the Disbursement report (if grouped by loan cycle, Namirembe Diocese, Uganda). to top 20. Corrected: the Repeat Clients/Loans report showed an incorrect Cumulated Outreach if printed for group clients (it is correct for Individual clients). For instance if user entered one group loan, the report with "count on clients" showed Renewed = 1 while Outreach = 0. For count on loans it was correct (Renewed = 1 and Outreach = 1). 21. Corrected: if a loan was disbursed in 2 instalments, the Loan Disbursement report showed a wrong total loan amount in the report summary (World Hope, Haiti). to top 22. Corrected: if a first loan was entered for a group with member gets ind. loan and user deleted repayments, disbursement, approval and modified the loan, the loan cycle for the members on the third page of the loan application was incorrectly showing that this is a 2nd loan. 23. Corrected: the importation of loan repayments for group loans with member gets individual loan was generating an error (File 24. Corrected: Rescheduled loans were not shown correctly on the Reprint Loan Repayment Schedule (ARD, Sierra Leone). 25. Corrected: if user choose to calculation loan provision on the outstanding principal balance, the provision report did not show the Outstanding Balance (Horizonti, Macedonia). 26. Corrected: if user printed the Indicators report for a period ending on an instalment date, the Indicator 'Portfolio at risk more than 120 days' was showing the amount that should have been under 'Portfolio at risk 1 to 30 days' (Incofin, Belgium). 27. Corrected: the Portfolio Analysis, first option, analysis by count on members did not give any output (Incofin, Belgium). 28. Corrected: the averages on the Portfolio Analysis, last option, performance indicators, were not always averages, but sometimes totals (like for PF at Risk). Now there are 2 lines, one for averages and one for totals. Also the 'total average' is now a calculated average on the basic data, not an average of the percentage of each geographic area (Incofin, Belgium). 29. Corrected: a report on deleted repayments gave an error message (Variable "TUserID" not found, World Hope, Sierra Leone). to top 30. Corrected: the booking of imported loan repayments for group loans with member tracking enabled was incorrect. The cash or bank account was debited with only the amount of the first member instead of the amount for the whole group. 31. Corrected: the importation of financial transactions did not check for existing transaction codes, making it possible to end up with the same transaction code for different transactions (Eclof, Kenya). 32. Corrected: the importation of financial transactions did not check the length of the transaction codes, making it possible to import non-standard size codes (Eclof, Kenya). 33. Corrected: the importation of financial transactions allowed for the importation of transactions without voucher number even if the voucher number was compulsory for all the transactions (Eclof, Kenya). 34. Corrected: the importation of financial transactions gave an incorrect message - "Amounts are too big" - if the transaction was not balancing (Eclof, Kenya). to top 35. Corrected: the importation of financial transactions did not log an error where a transaction was not balancing (debit and credit equal, Eclof, Kenya). 36. Corrected: the importation of financial transactions updated the transaction codes with the last transaction in the importation file, irrespective of whether this transaction was lower than the last Loan Performer transaction code (Eclof, Kenya). 37. Corrected: the Balance Sheet was showing an incorrect opening balance in the case when the report was printed for a period starting one or more years after the start of the financial year. In that case the transactions on that day were included in the opening balance (Namirembe Diocese, Uganda). to top 38. Modified: Loan Performer did not allow to run different instances (of Loan Performer) on the same machine. This could lead to problems if different users where connecting to Loan Performer via a VPN connection. Now each user uses his own resource file, so that this does not interfere with others. 39. Modified: the data-entry screen for group members, the importation module for the importation of group members and also the report on compulsory savings have been modified to allow for bi-weekly savings deposits (CIDR, Ethiopia). 40. Modified: the Savings Transactions report can now be filtered according to client categories (Mikrobank, Papua New Guinea). to top 41. Modified: a line has been added on the first page of loan application asking for the principal to be repaid at the last instalment. Loan Performer then divides the remaining principal over the n-1 instalments. This is only available for flat rate loans (textbox is greyed out if user changes to other than flat rate loan) and has no effect on the interest amounts due for each installment. In case of group loans, at the 3rd page of the loan application, Loan Performer has a second button to arrive at the repayment schedule for group members. This is called: Allocate to Members. In this case Loan Performer takes an equal percentage for the last due instalment for each group member. So if you have 300+400+500 (=1200) as principal for 3 group members, and you entered 1200 as the group loan amount with 600 to be repaid at the last instalment, Loan Performer would take 600/1200 times 300 for member 1, times 400 for member 2 and times 500 for member 3 for the last instalment at member level. So there is no recalculation like for the original button (CIDR, Ethiopia). 41. Modified: the Excel importation template has been modified to allow for the importation of the above loans (CIDR, Ethiopia). to top 42. Modified: the user can now set a background picture of his choice (Configuration/Users). 43. Modified: a feature has been added to the menu item "Postpone due dates" (second pageframe page) that makes it possible to change the instalment period between 2 dates. This makes it possible to change a weekly loan into a monthly loan. The amounts due don't change, only the due dates. User can select a range of loan (from loan number <1> till <99999> or all loans) and user can select on loan product. The starting date of the period has to fall in the future so that no repayments have been entered yet (CIDR, Ethiopia). 44. Modified: the Collection Sheet can also be printed for group loans (Village Banking). Before this was only available for group member loans (Grameen Banking, CIDR, Ethiopia). to top 45. Modified: the Collection Sheet has got an additional format (Loan No, Name, Loan balance, Some columns for Actual Collection and some for Expected Collection, including 2 savings products, CIDR, Ethiopia). 46. Modified: the menu option Group Members Repayments is now also available for repayments of group loans that are tracked at member level (not only for Grameen type loans). This repayment screen also has a possibility to enter savings deposits (positive amounts) and withdrawals (negative amounts) for 2 different savings products, which can be set by the user (CIDR, Ethiopia). 47. Modified: the Group Members Repayment report also shows the disbursement date (CIDR, Ethiopia). 48. Modified: the Outstanding Balances report has an additional report format (no. 7) that includes penalties and arrears (Soroti District Development Program, Uganda). to top 49. Modified: at Loan Application, user can change the due dates of half-monthly loans to any date of the month (Enterprise-Mentors, USA). 50. Modified: at Loan Application, second page, the user can now update all installment dates by modifying the starting date and clicking the Reset button (Enterprise-Mentors, USA). 51. Modified: the Outstanding Balances, the report Portfolio at Risk per credit officer and Arrears Report have gotten additional templates with telephone and address information (Enterprise-Mentors, USA). 52. Modified: the template for importation of loan applications has additional columns that indicate 1. whether interest should be paid in the grace period and 2. the principal to be paid in the last instalment (CIDR, Ethiopia). 53. Added: a Cash Flow Statement, where the user can define the label for an item and link the label to a total of 3 separate ranges of general ledger account numbers (CIDR, Ethiopia). to top 54. Added: Loan Performer now supports loans that are tied to a foreign currency. A table with exchange rates has been added and a loan can be tied to a foreign currency. If during the loan period the local currency decreases in value, the amount to be paid is more than the initial amount due. The excess is posted on separate GL accounts for "Exchange rate fluctuations for Principal" and "Exchange rate fluctuations for Interest and other fees". It is possible to (un-)tie existing loans to the foreign currency, so that repayments for an existing port-folio can be linked to the exchange rate fluctuations (Viator Azerbaijan, TMD Nicaragua, ACTED Tajikistan, Hope). to top
|
||