1. Corrected: if user was logged in as a French user, the formatting for data-entry screens had changed so that a point was used as the 1000 separator for numbers and a comma for decimals. However the reports still showed the English formatting (MFD).

2. Corrected: Spanish and Russian users now also get the point as the 1000 separator for numbers and a comma for decimals.

3. Corrected: some screen items did not default to the user-indicated font (see Configuration/General). Especially in Russian and other non-European character sets, this caused these screen items to be unreadable.

4. Corrected: once user entered a closure date for an account, it was final and could not be un-done (MFD). 

5. Corrected: user was not able to close a savings account if client had a time deposit outstanding (Gamstar).

6. Corrected: the template for the importation of group members said that Member Categories 1 and 2 had to be entered as text strings. This was not correct, they are numeric fields (Plan Fund).  

7. Corrected: the format No. 5 of the Clients report could not be printed if only group members were selected. If this is not a format for group members, then a suitable message should be given (Plan Fund).

8. Corrected: the Report on clients, State during a period gave an error message (Error number 1, saying “Thisform.summreport does not exist”).

9. Corrected: if a format was defined for a voucher number at configuration, the user could still enter a voucher number for a time-deposit that did not math this format.

10. Corrected: the entry of savings transactions and loan disbursements and repayments often caused users on a network to lock each other. In this version, we have used a different locking strategy for these transactions so that this problem is less likely to occur (KWFT, Plan Fund). 

11. Corrected: the entry of a bounced cheque for savings gave an error message (Error number 12, Variable “Sav...Acc” not found, MFD).  

12. Corrected: if user entered a loan application and modified one of the instalments with commission, the entry of a repayment would result in a negative commission balance.

13. Corrected: the modification of a loan application increased the loan cycle.

14. Corrected: if a user entered a loan application for a group client that was in arrears with the options “Group member tracking”, “Member gets individual loans” and “Follow up loan allowed if no arrears” enabled, Loan Performer displayed the right message but then disabled the whole menu leaving the user no option but to restart the program.

15. Corrected: when user repaid loans in arrears automatically from the savings account for a second time on the same day, Loan Performer posted the transactions with the same day-time stamp and got confused regarding the balances.

16. Corrected: if group member loan repayments were imported with tracking of member loans enabled, and user imported a loan repayment for several members of a group, the payments of the members were not saved and the Member Repayments report showed no loans repaid (Hope International).

17. Corrected: if user imported a pre-payment for a loan on declining balance with interest recalculated, this resulted in negative principal balances (BPH Haiti).  

18. Corrected: the “Principal Due” in the report “Payments made in a period” was incorrect (Vedco).

19. Corrected: the Loan Repayment Schedule did not produce the original dues but the modified dues because of pre-payments (Vedco).

20. Corrected: the Pre-Paid column of the Loan Status report always showed zero amounts. For loans on declining balance where interest has been recalculated at repayment, there is indeed no pre-paid interest. However for all other loans, there is (SPBD Samoa).

21. Corrected: the Portfolio at Risk report used to print a second report with a summary with sub-totals if grouped on loan officer, by branches, by fund etc. This had disappeared in version 6.15 (Terudet, UWFT).

22. Corrected: the summary option of the Portfolio at Risk report did not give sub-totals if grouped on loan officer, by branches, by fund etc. It only gave a total figure at the end of the report. This was not the scenario in previous versions (Terudet, UWFT).

23. Corrected: the Loan Status report for group members had a column for savings balances for 9 out 10 of the available formats. This has disappeared when the savings products were introduced. Now user can select a savings product and the report is being printed with the balances of that particular product (KWFT).

24. Corrected: the percentage of interest not paid on the Indicators report showed 1 instead of 100% if the paid interest in the period was zero (Incofin).

25. Corrected: if a loan was disbursed on the last day of the month, this was not included in the indicator Amount Disbursed on the Indicators report (Incofin).  

26. Corrected: the Indicators report still gave wrong amounts for the principal in arrears end of period as well as the interest in arrears end of period.  

27. Corrected: the value of items 7 and 14 - Number of clients/members with outstanding loans - of the Performance Monitoring report did not include loans disbursed in a former period (before the start of the financial year, CRS Turkey). 

28. Corrected: it was possible to update a general ledger account is such a way that the sub-account number equaled the header account number. This resulted in the deletion of the original account from the system if you choose to retry all the way. User would get a bug whenever a reference to the chart of accounts was made. 

29. Corrected: an error was generated when user selected menu item Accounts/Book Arrears > 90 days (Property “Caption” is not found) and the command buttons had no labels.

30. Corrected: if user defined a different chart of accounts, it was possible that the Sub-Account referred to a wrong header account at Chart of Accounts.

31. Corrected: the “Breakdown per account” report created an error if the grouping is by date or donor.

32. Corrected: the option “Additional Checks” under menu Tools/Check on data entry, created an error when checking whether all loan repayments have principal correctly booked into the GL.  

33. Corrected: if for a certain bank, some cheques were in the clearing and user changed the label of the bank at Configuration/Banks, he was unable to clear the cheques.

34. Corrected: setting targets (menu System) produced an error ("Datatype mismatch").

35. Modified: the Amyuni PDF driver (used for printing reports to PDF file formats) has been updated to version 2.10.

36. Modified: the phone field for group members has been extended to 40 characters (Plan Fund).

37. Modified: due dates can be scheduled to fall on a certain days of the week (at 2nd page of the loan application, Wasasa, Buusaa).

Updates in version 6.16 (of 28 February 2004)

1. Corrected: in some cases, user could get corrupted resource files. They would show up as a message at startup saying “Unknown error encountered, please inform Crystal Clear Software Ltd.” and Loan Performer would shut down. User could resolve this error manually by doing a file search on the hard disk for all Foxuser.* and Resuser.* files and deleting these. In version 6.15 the Loan Performer installation procedure searches these files and deletes them.

2. Corrected: the patch for updating the database checks on general ledger transactions where the account number is empty. These are then linked to the cash account and user can review these in the text file EmptyAcc.txt, saved in the LPF616 directory.

3. Corrected: if user closed a savings account, the balance could not be withdrawn if a minimum balance was in place.

4. Corrected: the report of Charges and Rewards for group members repeated the first name of the group.

5. Corrected: the entry of a bounced cheque that was a savings deposit gave an error message (error 1734, “Property cSavProdID not found”, MFD).

6. Corrected: if user entered a deposit/withdrawal to the Loan Revolving Fund at Configuration/Funds and tried to delete it, (s)he would get an error.

7. Corrected: if user entered a final pre-payment for a loan on declining balance with interest recalculated, this resulted in negative principal balances.

8. Corrected: if user had defined sub-accounts that had just zero’s after the main account number, Loan Performer classified these as Header accounts and did not show the balances on the financial reports.

9. Corrected: Loan Performer generated an error (“Unknown member OACCPage3”) if, after the entry of a manual transaction, the user indicated that (s)he did not want to continue.

10. Corrected: updating the General Ledger with menu item Accounts/Book arrears >90 days.

11. Corrected: Loan Performer generated an error (Error no. 3 “File is in use”) if user had defined a budget item, did not define any budgets, but linked it to an account and ran the Budget report for the first year.

12. Corrected: if an earlier database with a Parmec chart of accounts was updated, accessing the chart of accounts gave an OLE Dispatch error.

13. Corrected: the Tools/Check Database option “Check on Debit and Credit in Genledg” was not working properly in all cases. It was possible that corrections were made, but then when the user ran the same procedure again, the correction did not correct the transaction. 

14. Corrected: the “Save” button on the last page on Configuration/Define Labels (transaction labels) was not working.

15. Modified: the list of menu items at Configuration/Define Labels, page 4, has been set in alphabetic order.

Updates in version 6.15 (of 12 February 2004)

1. Corrected: if user worked without a license and modified the path to the database at Configuration/General but then returned the original value in different upper/lower case, (s)he was not able to save as Loan Performer said “The new database does not have a corresponding license file installed. Make sure you copy the correct LPF.KEY to this directory. You will stick with the old database for the moment.”

2. Corrected: at startup, before the login, Loan Performer said that the program is compatible with Windows 95/98/2000/ME but XP was not mentioned.

3. Corrected: if user entered a loan fund and indicated that Loan Performer should not book transactions into the general ledger, (s)he was not able to add another loan fund where this was not the case.

4. Corrected: in menu System, both the items User Log Report and Login/Logout used the same shortcut key (the key “L”). The user could select only the User Log Report with the shortcut and not the Login/Logout.

5. Corrected: the sub-items of the Tools menu were not accessible from the menu Configuration/Set User Access Rights.

6. Corrected: the date picker controls for the start of membership date and the birth date on the group members’ form were not visible, (they would only appear when clicking on another group member page and returning).

7. Corrected: when a member of a group was transferred to another group (s)he still retained his/her board function,  irrespective of whether the other group where (s)he is transferred to, already has it’s board of governors.

8. Corrected: it was possible to open a savings account before the registration date of the client.

9. Corrected: if user entered a new client by first going into the Savings page, clicked on an empty row in the savings account list, then opened up a new savings account and then entered the other details of the client (name, address etc), then, after saving the registration fees, an error was generated (Error number 9: “Data type mismatch”).

10. Corrected: client and loan categories have been put in alphabetic order at entry of new clients and loans.

11. Corrected: if user wanted to close a savings account and went into the Client Profile (menu Clients), clicked on the Savings page and selected the Savings Account, then choose a closing date using the mouse, Loan Performer did not show the textboxes for Reason for account closure and Account closure fees (Gamstar).

12. Corrected: if client had several savings products and user closed one of these, Loan Performer closed all.

13. Corrected: the importation of Client data did not show the progress with the number of clients out of a total being imported, just like importation of savings and loans.

14. Corrected: the importation of Guarantors gave an error (“Must specify additional parameters”) and was not possible.

15. Corrected: photo and signature references of guarantors were not saved when guarantors were imported.

16. Corrected: the report on Clients/State during a period could not be exported to PDF.

17. Corrected: if a group savings account was closed and a charge was entered as closing fees and group savings were tracked at group member balances, Loan Performer posted the charge to the group only but not to the members. Now Loan Performer does not allow the user to enter a charge if groups are tracked at member level.

18. Corrected: it was possible to backdate the date of a savings transaction to before the client’s registration date via Modify Transaction.

19. Corrected: the Client report, if printed for clients with outstanding loan balances, did not show any clients if these were imported and not manually entered  (UWFT).

20. Corrected: the ID number of clients was not shown on the report fort Blacklisted clients (however it is shown if the report is run for a period, MFD).

21. Corrected: when a client had been blacklisted and later again de-blacklisted, the entry of a savings transaction still warned that client was black-listed (SPBD).

22. Corrected: the receipt for buying shares was completely messed up if the client had a long address (MFD).

23. Corrected: if user entered deposits or withdrawals for groups with group member tracking enabled, the user could type in amounts in the grid on the third page for the group members, then when clicking the “Update” button, an error message was generated (“Please select transaction then  press <Update> button”, Acord Ethiopia).

24. Corrected: in version 6.07 the restriction of not being able to modify savings charges and rewards was dropped. However, the message that there is no option to correct charges or rewards still appeared while calculating charges and rewards.

25. Corrected: if charges are entered it was not necessary to make a printout. Now this is compulsory (MFD).

26. Corrected: the Savings Withdrawal Slip did not show the savings product nor the voucher number.

27. Corrected: the modification of a savings withdrawal to another date, could lead to an incorrect message saying “Savings balance will become negative, transaction not allowed” as Loan Performer would not consider the annulment of the initial transaction (Gamstar).

28. Corrected: Loan Performer could refuse the modification of the date of a savings withdrawal saying “Balance will be less than zero”, although this would not be the case (Gamstar).

29. Corrected: the interest calculation gave wrong balances for interest additions for accounts that had transactions on the same day (Mucoba).

30. Corrected: the importation of several savings transactions on the same day could lead to wrong end balances in Loan Performer as the import file only had a date stamp and no time indication. Now Loan Performer treats the first transaction found as the earliest and adds later time-stamps to following transactions.

31. Corrected: the importation of savings deposits with stationery and or commission led to incorrect bookings into the general ledger.

32. Corrected: the receipt for a Time-Deposit showed the interest amount for one year, even if the client made a deposit for less than a year (MFD).

33. Corrected: user was able to import the group member savings on a database that was tracked at group level without any notification.

34. Corrected: user could transfer amounts from one savings account to another without any printout (MFD).

35. Corrected: the Savings Balances report would give an error message if printed for group accounts, only dormant accounts and Order by name (error: “Name is not unique and must be qualified”).

36. Corrected: the State of Accounts report, if run for a period, did not show the number of dormant and re-activated accounts correctly.

37. Corrected: the Group Member’s Period Savings report showed the savings balance but not the amounts saved in the specified period.

38. Corrected: the Period Balances report, when printing quarterly reports, the third quarter has its year figure missing the last digit.

39. Corrected: the Day-Sheet for Savings showed an incorrect amount for savings deposits (under Part A).

40. Corrected: the Savings Tillsheet could not be printed for officers that were not defined as “Savings officers” (Mucoba).

41. Corrected: the report Personal Ledger (menu Savings) did not show anything for a client who had only bought shares but had no savings accounts. Loan Performer even gave a message that the client code did not exist (MFD).

42. Corrected: the Personal Ledger report for all clients gave an error message if the date/time picker was used (“Property Fday not found”).

43. Corrected: the amounts due for loans with Declining Balance Amortised were not the same for every installment. The amounts due for the last installment were always different. Now the total of principal and interest is equal for each installment (Mikrofund).

44. Corrected: if user entered a search item like ‘credit’ in Configuration/Define labels and clicked “Fuzzy”, (s)he would get many hits. If user selected one item, then clicked on “Pick” and overwrote the item with the same word and clicked “Fuzzy” again, the number of items would be much less.

45. Corrected: if user renamed the label of the credit officer at Configuration/Define Labels and used lower case, (s)he could not enter new loan applications anymore (Loan Performer was saying “No credit officers found, please enter first your credit officers”, WEEC).

46. Corrected: negative collateral values were permitted for collateral at loan application and modification of loan application.

47. Corrected: if loan tracking was at group member level and member would get an individual loan (Grameen model) and user entered loan application and clicked on the button “Check Savings”, sometimes an error was generated (Error number 1234: “Subscript is outside defined range”).

48. Corrected: if Savings were linked to Loans in Configurations Loans Part 3 and user entered a loan application and then modified the loan application, the field for Savings Balances Needed showed incorrect values and the loan might be refused (KWFT).

49. Corrected: when user entered a payment of commission from the menu Loans/Payment of Commission and entered an amount that was not available on one of the savings accounts and indicated that this had to be paid from the savings account, Loan Performer would show an incorrect message (“Cash Accounts” plus balance, “Add or modify cash accounts” plus balance, “Please enter an account name”).

50. Corrected: the loan disbursement of a semi-annual loan on declining balance with recalculation of dates and interest amounts generated an error (Error number 9: “Data type mismatch”, Acord Ethiopia).

51. Corrected: the menu item “Report due dates” has been replaced by “Postpone due dates”.

52. Corrected: selecting savings transfer when entering a loan repayment and then double clicking the list box resulted in an error.

53. Corrected: printing of receipts was not possible for loan repayments for group loans with member tracking enabled and the option “Member gets individual loans” activated and using menu option “Loans/Group Member Repayments”. If the normal menu option was chosen (“Loans/Repayments”), printing of receipts was okay.

54. Corrected: the receipt for loan repayments for group loans with member tracking enabled and the option “Member gets individual loans” activated, mixed up the identity card number with the loan number.

55. Corrected: closing a loan with declining balance did not give the correct balance if no interest was to be recalculated at loan repayment (MFD).

56. Corrected: the module Group Member Repayments was not working properly for loans on declining balance. Loan Performer booked prepayments on a wrong date and then if the group had different loans with payments at different times, Loan Performer took the dates for the first loan of the group and not the current loan (KWFT).

57. Corrected: if user imported a repayment for a loan that had penalties, the allocation to the penalties was not correct.

58. Corrected: if user choose menu item Repay Arrears from Savings to repay group loans that were tracked at member level, Loan Performer withdrew savings balances from the group but not from the members.

59. Corrected: if user entered group member repayments for a group with configuration set to “Member gets an individual loan” and added stationery amounts, the booking to the general ledger did not include the stationery amount in the cash/bank amount.

60. Corrected: the voucher number was not saved in the database at importation of loan repayments (World Concern).

61. Corrected: if user deleted a loan that was disbursed via the client’s savings account, the report Outstanding Balances for Savings would show a correct balance (corrected with the deleted disbursement), however the Savers Statement (and also the Group Members Statement) would still show the balance including the disbursement.

62. Corrected: if user entered a loan repayment for a group loan and closed the loan, the interest to be paid was more than the interest balance, resulting in negative interest balances (ID Haiti).

63. Corrected: if user deleted a loan repayment that closed the loan and cancelled the remaining interest, the original interest was not reset.

64. Corrected: if in a situation where savings were tracked at group member level and loans at group level, user entered a loan repayment from the savings account, the group savings balance was updated correctly, but as Loan Performer did not know the payments of each member, the group member savings balances were not updated, causing inconsistency between group and member balances. Now an appropriate validation message has been put in place to disallow this posting.

65. Corrected: Loan Performer applied a grace period for every time that penalties were calculated, even if a loan was in arrears at the start of the period and the grace period was given in the last penalty calculation (Mikrofund Bulgaria, Incofin).

66. Corrected: the 3rd option on the configuration page for penalties (“Penalties calculated as a percentage over the period”) just calculated penalties as if the period was 12 months (Acord Ethiopia, Teso).

67. Corrected: if user defined penalties as a flat amount per day and no penalties on non working days, Loan Performer still calculated penalties for non working days in case there was an arrears for the first installment (Incofin).

68. Corrected: the calculation of penalties is per product, however the penalty report did not show this.

69. Corrected: the Loan Status was not changed to “Fully Repaid” after user entered the last repayment for a loan on Reducing Balance.

70. Corrected: the Loan Status of loans with deleted repayments or deleted disbursements/approvals was incorrect at menu item Retrieve Loans.

71. Corrected: if loans were tracked at group member level and later user changed the configuration to track at group level, an error occurred at entry of repayments for loans that were entered before the configuration was changed ("Error number 1925").

72. Corrected: the entry of a loan repayment before the last repayment that was entered, was not working properly (Foccas, KWFT).

73. Corrected: if due dates were postponed or advanced because of non-working days on loans on declining balance where interest was calculated in days, the interest was not recalculated because of the extra days even if user indicated so at disbursement (Vedco).

74. Corrected: if interest was recalculated at time of loan repayment for loans on Declining Balance (whether amortized or discounted) and with interest in days, the recalculated interest was different than the interest calculated at loan application even if the user paid according to the initial schedule.

75. Corrected: the recalculation of interest for loans on declining balance was inconsistent between group balances and group member balances. The group member balances were incorrectly updated (KWFT).

76. Corrected: the entry of a pre-payment for loans on declining balance amortized sometimes resulted in negative principal balances and Loan Performer refused to accept additional payments (KWFT).

77. Corrected: the rescheduling of loans created an error when closing the window (“Cannot access selected table”).

78. Corrected: the rescheduling of loans sometimes showed loans that were fully repaid. If user selected them, (s)he got a message that loan was fully repaid, but then the menu items became in-accessible and user had to restart the program.

79. Corrected: writing off of several loans together made the computer “hang”.

80. Corrected: if a group member had a loan but because of pre-payments, he had no amounts due, the Group Members Savings and Collection Sheet printed just the name of the member and not the loan amount if printed for all members (SPBD).

81. Corrected: some reports were not printing properly and were having the right margins cut off (Incofin, Face to Face).

82. Corrected: the "Recovery of Past Due" report did not include payments that were made on the last day of the period, causing the “Principal Past Due” at the end of the period to be un-equal to “Principal Past Due” at the start of a consecutive period. The same with regards to the “Interest Past Due”(Incofin).

83. Corrected: the "Recovery of Past Due" report indicated at the bottom that “Loans that became past due during the period are not included” although they actually were part of the report. So this comment has been taken out (Incofin).

84. Corrected: the “Principal Past Due” and “Interest Past Due” - whether beginning or end of period - of the “Recovery of Past Due” report did not tally with the Arrears report for the same dates.

85. Corrected: the second date was not included in the heading for the report on Pre-Payments if printed for all loans (Incofin).

86. Corrected: the Portfolio Analysis Report, the first format (Analysis by count on Members, Groups etc.) could repeat a certain geographical area several times while this should occur only once (Wordvision Kosovo).

87. Corrected: if user asked to print the Portfolio Analysis report as a PDF file without specifying the PDF extension, files with extension TXT were created (Incofin).

88. Corrected: the Portfolio Analysis Report gave as Total Averages a percentage with 4 decimals (Incofin).

89. Corrected: the Portfolio Analysis Report with ‘Savings Analysis’ as portfolio type, gave 3 options for the report format plus 2 white lines showing “.F.”.

90. Corrected: the Indicators report could not run for different loan funds separately. It gave wrong figures that did not add up (Incofin).

91. Corrected: the number of outstanding loans and also the amount of outstanding loans at the end of period of the Indicators report was not correct if run for men or women separately. It just gave the total figures (Incofin).

92. Corrected: the Indicators report had wrong amounts for the following indicators "Principal in Arrears end of period", as well as "Interest Due in period” and “Interest in Arrears end of period" (Incofin).

93. Corrected: the Indicators report showed an incorrect percentage Interest Not-Paid (Incofin).

94. Corrected: the Category report (under Analysis Reports) inversed the items. For instance if Loan Category 1 was used and had items 1 and 2 and a loan was linked to item 1, it would show up as item 2 in the report (ID Haiti).

95. Corrected: the Portfolio at Risk report could not be summarized.

96. Corrected: the Portfolio at Risk report showed stars in the total field for large databases (Foccas, Terudet, UWFT).

97. Corrected: the footnote in the Arrears report speaks of ‘Principal at risk” instead of “Portfolio at risk”.

98. Corrected: the Arrears report for group member loans showed a loan as being for 2 installments in arrears while the Arrears report for groups showed only the last installment as being in arrears in case the group member paid the remaining principal of the first installment with the second installment without paying off the second installment completely (see Number of days in arrears).

99. Corrected: the report ‘Expected repayments for past and present dues’ showed a wrong header “Recovery of past due’. This should have been “Expected repayments”.

100. Corrected: if user wanted to print loans at a higher geographical area (higher than the parish level) and all clients were entered at the lowest level (the parish level), the loan reports did not show any loans. Only the Client Report did.

101. Corrected: when multiple Loan Ledger Cards were printed to file, only the last loan was saved to file. Now each Loan Ledger Card is printed to a separate file where the file name contains the loan number (NRDF).

102. Corrected: the report “Payments during a period” gave a wrong percentage in the last column.

103. Corrected: the Monitoring report for groups had the following errors:
     - No. of group members with outstanding balances showed a 1:1 correspondence i.e. it’s the number of loans outstanding rather than the number of group members with outstanding loans.
     - Loan amount of group members with first loan still outstanding showed the total loan amount of all installments, not the first one only.
     - No of group members with 2nd loan outstanding was wrong.
     - No of group members with 3rd loan outstanding was wrong.
     - Loan amount of group members with 2nd loan outstanding was also wrong.
     - Loan amount of group members with 3rd loan outstanding was also wrong.
     - The on time repayment rate for both principal and interest was wrong.
     - Percentage of portfolio at risk was correct only if active loans as of that period were not included.
     - Amount blocked in loans was incorrect. I.e. if loans have been linked to savings for guarantee purposes, then this amount should only indicate the amount used as guarantee.
     - if loans were deleted, the amount blocked in loans did not reflect the changes made!

104. Corrected: the Monitoring report could give an error saying “SQL: Column ‘Indicator’ is not found.”

105. Corrected: the Category Report caused an error if user asked for Outstanding Amounts by User defined Loan Category (error no. 1851, “Selects are not union compatible”).

106. Corrected: the report on Rescheduled and Written Off loans could be run “as after rescheduled” in earlier versions. This item has been removed as it made no sense.

107. Corrected: the total of arrears for the current month (Section 3, sub-section 52) of the Performance Monitoring Report was not equal to the total of items 47 to 51 (Five Talents).

108. Corrected: the Loan Size Analysis report often showed error message “Cannot access selected table” when called from menu.

109. Corrected: the item “Posting” should always show “No” for header accounts and should be grayed out so that it is not accessible.

110. Corrected: the window with the accounts at Chart of Accounts became distorted if not all account numbers had the same width (MFD).

111. Corrected: when updating an item in Chart of Accounts, if user affirms the account Number replacement but refuses the account Label replacement, the account number was not changed.

112. Corrected: it was possible to update an account is such a way that the sub-account number equaled the header account number. This resulted in the deletion of the original account from the system if you choose to retry all the way. User would get a bug whenever a reference to the chart of accounts was made. 

113. Corrected: if user decided to update an account but instead of selecting an account by using the mouse, (s)he typed the necessary values, Loan Performer behaved like adding a new account.

114. Corrected: the Importation of the chart of accounts resulted in a bug.

115. Corrected: if user had created a GL header account, then later removed the sub-accounts, the header account did not automatically become an account to which the user could post transactions (Gamstar).

116. Corrected: the Income and Expenditure statement for the Parmec chart of accounts included accounts in group 2 (“Pasif”, MDF).

117. Corrected: when entering a manual GL transaction and the user modified one of the debit/credit lines by clicking the Update button, the total debit/credit amounts were not refreshed.

118. Corrected: the deletion of the booking of manual transactions was not possible with “Accounts/Add or Modify Transactions” (MFD).

119. Corrected: when entering manual GL transactions and user entered an account on the first page or selected an account on page View Transaction, the View transactions per account page did not show the transactions of the selected account (Gamstar).

120. Corrected: when entering GL transactions, the combo box for the Double Entry Account allowed the user to select accounts that are headers or accounts that are not for posting and the transaction was saved without a problem.

121. Corrected: an error was generated if after saving a manual general ledger transaction, user selected to proceed with another transaction, but after inputting either the description or account field, (s)he presses the Cancel button (“Cannot access the selected table”).

122. Corrected: the Day-Closure report showed date and time, increasing the printout with 2 lines per item instead of just one. Now it only shows the date of the transaction.

123. Corrected: the Day-Closure report did not include transactions on the last date of the period.

124. Corrected: the booking of the modification of a shares transaction did not inverse the initial transaction with negative signs as all other corrections, but debited if the account was credited and vice-versa. Also the description did not indicate that this was a correction.

125. Corrected: many financial reports did not include transactions on the starting or ending date of the period (caused by the fact that in version 6.07 all date fields have changed into date-time fields).

126. Corrected: if user had closed financial years the reports that covered periods in current and past years caused errors because the tables for the closed periods were not updated with the same date-time field.

127. Corrected: if user had not entered the financial year and entered savings transactions, then entered the financial year and modified those savings transactions, the booking of the modification was incomplete, resulting in debit and credit balances not being equal anymore.

128. Corrected: there was a difference in the Help file and the booking of interest for Time-Deposits. The Help file said that the interest is booked when user calculates the interest and the “Interest Due on Time Deposits”, a liability account in credited. Then when user enters the withdrawal, the “Interest Due on Time Deposits” is credited. However this was not the case. At calculation of interest, nothing was booked and the interest was only booked at withdrawal. The liability account was not affected at all (Gamstar).

129. Corrected: the booking of Accrued Interest was incorrect if user had calculated Accrued Interest in the past financial year, updated the GL accounts, closed the financial year, and calculated Accrued Interest again. The problem was that the Accrued Interest in the past financial year was taken as profit and the profit account became zero. The first time Accrued Interest was calculated in the new year, it would post the full amount of interest in arrears as profit. This was incorrect as a part of this had already been taken as profit in the past financial year. Loan Performer has resolved this by only taking the Interest in Arrears minus the Asset accounts “Accrued Interest Due”.

130. Corrected: if user deleted one of the lines of the entry of a manual financial transaction into the general ledger, an error was generated (Error number 5: “Record is out of range”).

131. Corrected: if user modified a manual entry in the general ledger and deleted one of the lines of the financial transaction, an error was generated (Error number 5: “Record is out of range”).

132. Corrected: when posting manual transactions on a networked database from several workstations, user could get an error message (Error no 108) when clicking the Save button, saying “File is in use by another user” (Eclof Kenya).

133. Corrected: the combo-box for selection of an account when entering manual transactions was not showing every non-header account.

134. Corrected: if transactions were deleted, the Breakdown report showed incorrect balances on the same line of the transaction as it could not make a distinction which line came first. However the account balances at the end were correct (UWFT).

135. Corrected: the report created on the second page of the Breakdown report specified the period as set on the first page of the form and not as specified on the second page.

136. Corrected: the Totals of Debit and Credit of the Breakdown report did not include transactions on the starting date of the period and transactions on the ending date of the period, although these were listed in the report.

137. Corrected: if start of financial year was not on 1/1 and user entered a budget for current calendar year without, entering a budget for the last calendar year, the budget report showed a wrong total for Budgeted YTD.

138. Corrected: the Balance Sheet produced similar reports for both detail and summary options.

139. Corrected: if the Profit per Period report was asked for less than the current month, it still reported until the current date.

140. Corrected: dividend (or ‘trop perçus’ in the Parmec chart of accounts), is not a charge, but an allocation of the net profit of last financial year. So it had to be booked to  “Créditeurs divers (351- Trop perçus à verser)” before it was being credited to the account of the member.

141. Corrected: user could not update Client/Loan or Member categories if the labels had the same base word (e.g updating “citizenship” to “citizen” was not possible).

142. Corrected: if due dates were updated at cheque clearing, user could get an error when (s)he choose not to recalculate dates (error “Operand/operator mismatch”).

143. Corrected: importing the branch data into the corporate database deleted the start of financial year (and disabled it as well).

144. Corrected: if user selected a database for importation and canceled the operation, the branch code had changed to the new database.

145. Corrected: only the fund of the first imported database was imported when creating a corporate database. However, at Configuration/Funds, the fund deposits of all funds in all databases were cumulated under only one fund while, if these transactions were booked to different GL fund accounts, they were correctly imported into the corporate GL.

146. Corrected: if user entered a loan fund, then deleted the fund and re-entered a fund, without doing a Purge, (s)he would not be able to save the new fund. Loan Performer would give an error message (“Something went wrong, no information saved”).

147. Modified: now it is possible to restore the database into an empty folder. This used to be only possible if the folder contained a Loan Performer database.

148. Modified: if user wanted to restore a database and confirmed that the current database could be deleted and did not have backup files in the selected folder, Loan Performer could not be restarted with the same database folder as this would be empty now. In this version Loan Performer will check first whether the backup files are available before deleting the current database.

149. Modified: the backup and restore windows now have a “Select” button where the user can choose a folder.

150. Modified: if user enters a folder at backup that does not exists, Loan Performer asks the user whether (s)he wants to create this new folder.

151. Modified: the creation of a backup and the restore window show the date of creation of the last backup (this is the file creation date, Incofin).

152. Modified: the exportation of the Clients reports – for individual clients and group members – also exports the client’s birth date so that users can analyze reports also according to the clients age.

153. Modified: a “New GL Account” button is added on Configuration/Shares.

154. Modified: the page Configuration/Corporate Update Settings has been removed (and all code and help items that go with it).

155. Modified: the registration of clients of less than 10 years old was not allowed in former versions. Now the user can set the minimum age on Configuration/Register Part 2.

156. Modified: user can now link to fees for savings account closure to a specific general ledger account.

157. Modified: user can now link to fees for bounced cheques to a specific general ledger account.

158. Modified: user can now link each product to a different GL account. A combo box with (shares/savings/loan) products is added to each respective configuration page for Shares, Savings and Loans (Woccu, NRDF, UWFT).

159. Modified: a “Reset” button has been added to the importation forms so that the list of imported files can be cleared.

160. Modified: a checkbox has been added the "Recovery of Past Due" report that eliminates all loans that are not in arrears at beginning and at the end of the period (Incofin).

161. Modified: the menu item Accrued Interest can now also be used for the posting of accrued interest on savings (Woccu).

162. Modified: the Balance Sheet now indicates whether a profit has been made or a loss. In earlier versions it showed just a “Profit and Loss” label where it was not clear whether this was a profit or a loss.

163. Added: the menu item Savings/Personal Ledger Balances has an additional page where a report can be printed with savings and loans balances for a period (Worldconcern).

164. Added: user can now update the general ledger accounts with loans that are in arrears for 90 days or more (MFD).

Updates in version 6.14 (of 26 September 2003)

1. Corrected: if user restored a backup, the restoration went well, but afterwards (s)he would get an error (error 1733, saying: “Class definition Datetimepicker not found”, SPBD Samoa).

2. Corrected: if a deposit for a group member was entered (tracking for savings at group member level is activated) and user continued with a second transaction for the same account, the window with transactions for the group members was displaced (SPBD Samoa).

3. Corrected: if user entered a savings deposit, then continued with a withdrawal for the same account, the label “Amount” suddenly changed into “Free Savings” (SPBD Samoa).

4. Corrected: if loan tracking for group members was enabled and group member gets individual loans (Grameen methodology), and member was transferred to another group, the loan reports did not show anymore the loans that the member received in the first group, also when these reports were run at group level (see for instance Disbursement Report, SPBD Samoa).

5. Corrected: if a loan repayment for a group member was paid from the savings account of that group member and group members would get individual loans and savings was tracked at group member level, Loan Performer updated the group savings correctly but did not update the members loan. The situation became worse at the general ledger level if user deleted this transaction.

6. Corrected: when a user ran the module "postpone due dates", the  program blocked and user would  have to restart the program (Mikrofund Bulgaria).

7. Corrected: when user re-scheduled group loans with tracking at member level enabled, updating group dues created an error (“Error number 10 occurred …”).

8. Corrected: if user clicked on Update Group Dues with rescheduling of group loans with group member tracking enabled, an error occurred ("Error number 10").

9. Corrected: the last digit on the Breakdown and Summary of the Day Closure Report was not visible if printed on some printers (Face to face UK, SPBD Bulgaria).

10. Corrected: if user entered a financial transaction manually and had modified and deleted transaction lines, when adding a new line, he would get an error saying: "Voucher number can not be empty” in case voucher number was set as compulsory in the configuration. However this field was disabled.

11. Modified: middle name has been added for Guarantors (SPBD Bulgaria).

Updates in version 6.13 (of 4 September 2003, not available from this site)

1. Corrected: if user tried to restore the database and indicated a source drive that was not available, Loan Performer would inform the user correctly, but then an error message was generated – saying: “File ‘…\myerrors.dbf’ does not exist” – leading to a corrupted database.

2. Corrected: the LPFIndex had a problem making it impossible to start Loan Performer again if user ran executed this file.

3. Corrected: if user used the “Other” language field for non-western languages, these became unreadable on Window95/98 machines. The “Other” language field has changed to binary field type (Mikrofund Bulgaria).

4. Corrected: the Break-Down report gave incorrect balances if several transactions took place on the same day.

5. Corrected: financial reports did not include transactions on the last day of the month.

Updates in version 6.12 (of 29 August 2003, not available from this site)

1. Corrected: the Loan Performer setup did not install all files needed for installing the PDF generator on Windows XP machines. On a side note: installation needs administrator rights for Windows XP, so make sure when logged in, you have those rights.

2. Corrected: the English Help was showing weird characters on the Index page and the file was not context sensitive.

3. Corrected: the rounding of principal and interest at loan application was inconsistent. A Rounddown button is added and the Round-left button has become a normal Round function (Mikrofund).

4. Corrected: importation of clients for a multi-branch license gave the error “Incorrect Client Code”, even if client code was one of the available branch codes (WEEC).

5. Corrected: if a repayment was made for loans on declining balance with member tracking enabled and interest was to be recalculated, the Update button for the group member payment reversed the interest to what is due according to the installment date and did not take into account any pre-payment (KWFT).

Updates in version 6.11 (of 21 August 2003, not available from this site)

1. Corrected: if a new individual or group is entered in a centralized database (with several branches) and the client record was modified, the user could give a new branch code, but this is (correctly) not saved. However with a business record this was not the case, resulting in lost savings balances etc.

2. Corrected: the entry of groups generated an error if the tab button was used to move back and forth through the group members tab-page.

3. Corrected: if user opened the Group clients window and double clicked on the combobox for the board members, while no members had been defined, an error was generated (Error no. 107, operator/operand mismatch).

4. Corrected: if at entry of clients, user selects a particular item on pages “Savings Details” or “Loan Details” and saves, the sex combo box and the loan ledger card became misaligned.

5. Corrected: retrieving clients after a previous retrieval did not automatically refresh the Savings Details page. 

6. Corrected: the Savings Withdrawal and Deposit windows did not reflect the number of signatories needed for withdrawals for individual clients.

7. Corrected: the entry of payment of loan commission for group loans with member tracking generated an error (no. 1234 “subscript is out of defined range”).

8. Corrected: the item on rescheduling was not correctly implemented in the last version. For group loan with member tracking enabled, the due dates of the members did not tally with those of the group.

9. Corrected: the first report format for the Guarantors and Collateral report showed an arrears amount even if the loan has not been disbursed. The second report format showed an outstanding amount and a disbursed amount if the loan has not been disbursed.