This page was last updated on

26/07/2008 11:17:23

For 7.10 only

You will find the latest correction of 7.10 by clicking here.

1. The conversion of a Foxpro database to SQL Server automatically sets a closing date for the loan fund under Configuration/Funds (BTrackerID 4140). This is fixed in binarytochar.exe (click to download).

2. If user installed a license into an unlicensed database, the 'Branches' field in the Users table was not updated (BTrackerID 4131, Paidek, DR Congo). This is fixed in LPF 7.10.08.

3. When logging into Loan Performer, if the database had time-deposits, user got an error ("Function, argument, type or count invalid", BTrackerID 4212, Coopec-Nyawera, DR Congo). This is fixed in LPF 7.10.08.

4. Installation of LPF in another language other than English gave an error ("Uniqueness of index Langname is violated", BTrackerID 4168, Al-Halaal, Rwanda). This is fixed in LPF 7.10.08.

5. Error at menu Clients/Individuals, Groups and Business clients ("Property <GetCoAccountHolder> not found", BTrackerID 4175). This is fixed in LPF 7.10.08.

6. Importation of Individual Clients without ID documents was impossible even when ID documents were not mandatory (BTrackerID 4195). This is fixed in LPF 7.10.08.

7. Error at guarantors when user clicked on the filter button and then on the print button (BTrackerID 4137). This is fixed in LPF 7.10.08.

8. The Client Report for Active Group Members with Outstanding Balances did not give the same number of group members as the Group Members Outstanding balances. BTrackerID 4153, Hekima, DR Congo). This is fixed in LPF 7.10.08.

9. The Report on client ID documents did not show the selection made (BTrackerID 4193). This is fixed in LPF 7.10.08.

10. Receipt printing at the sale of shares is added (BTrackerID 4200, Mtoni, Tanzania). This is added in LPF 7.10.08.

11. If user entered accidentally a buying of shares from the savings account instead of a sales and corrected this, LPF booked correctly the cancellation of the original transaction but for the new transaction, the shares account was debited correctly but the account number of the savings account was left open for the credit part of the transaction (BTrackerID 4187). This is fixed in LPF 7.10.08.

12. User can now also search by co-account holder when making deposits (BTrackerID 4173, Malanga, Mozambique). This is fixed in LPF 7.10.08.

13. Savings deposit and withdrawal slips now show the client's reference number if not empty (BTrackerID 4150, Al-Halaal, Rwanda). This is fixed in LPF 7.10.08.

14. A  new receipt format (AL-Halaal) is added for savings deposits and withdrawals (BTrackerID 4172, Al-Halaal, Rwanda). This is fixed in LPF 7.10.08.

15. Printing of a range of savers statements is added (from account: ... to account: ..., BTrackerID 4134, Ned-Consultants, Nigeria). This is added in LPF 7.10.08.

16. A format with name of the client is added to the Savings Tillsheet (BTrackerID 4166, Al-Halaal, Rwanda). This is fixed in LPF 7.10.08.

17. Order options added for Savings Tillsheet (options: day-time, transaction code, voucher, BTrackerID 4165, Al-Halaal, Rwanda). This is fixed in LPF 7.10.08.

18. If receipts were saved to PDF into a given folder, the deposits were saved but not the withdrawals (BTrackerID 4202, Mtoni, Tanzania). This is fixed in LPF 7.10.08.

19. LPF allowed a withdrawal from the client savings account even if there were un-cleared cheques (BTrackerID 4198, Al-Halaal, Rwanda). This is fixed in LPF 7.10.08.

20. Importation of savings transfers for the same client on the same day on the same account gave wrong balances (BTrackerID 4174, Al-Halaal, Rwanda). This is fixed in LPF 7.10.08.

21. When importing Savings transactions or Loans Disbursements, if the GL Account had more than 6 characters, LPF said that the GL account did not exist (BTrackerID 4181 and 4186, Coopec-Nyawera, DR Congo). This is fixed in LPF 7.10.08.

22. The Importation of Savings transactions without any of the transactions being a withdrawal, created a run time error (BTrackerID 4180). This is fixed in LPF 7.10.08.

23. The savings till sheet has an option to print both the Reference number and the Client Name (BTrackerID 4179, Al-Halaal, Rwanda). This is fixed in LPF 7.10.08.

24. The Group Member Savers Statement gave incorrect balances if run for different periods (BTrackerID 4218, Buusaa Gonofa, Ethiopia). This is fixed in LPF 7.10.08.

25. User can import Time Deposits (BTrackerID 4188, Coopec-Nyawera, DR Congo). This is fixed in LPF 7.10.08.

26. Added <Grace Period> and <Cheque Number> to loan contract variables (BTrackerID 4154, Mecap, Senegal). This is fixed in LPF 7.10.08.

27. If user attempted to enter a loan repayment direct to a bank but no banks had been defined and the listbox would stay empty, (s)he would get a bug (Operator/Operand don't match, BTrackerID 4141). This is fixed in LPF 7.10.08.

28. A loan repayment of an individual loan that has been written off, was booked to the wrong  account (124120 instead of 420090 in the demo database, BTrackerID 4155, Hekima, DR Congo). This is fixed in LPF 7.10.08.

29. Deleting a Loan Repayment without selecting a loan, deleted all repayments in the database (BTrackerID 4148, Kazoza Vision, Burundi). This is fixed in LPF 7.10.08.

30. The deletion of loan disbursement created a bug in selected databases (Variable <NrIn> is not found, BTrackerID 4123, Bancs Microfinance, Uganda). This is fixed in LPF 7.10.08.

31. Importation of Loan Disbursement with commission deducted gave an error ("Property TCode not found", BTrackerID 4210, Habitat, Costa Rica). This is fixed in LPF 7.10.08.

32. Importing loan repayments by savings transfer gave an error about savings product not being found (BTrackerID 4214, Habitat, Costa Rica). This is fixed in LPF 7.10.08.

33. The Importation of loan repayments with Mode = 4 (direct to bank) was not possible (BTrackerID 4215, Habitat, Costa Rica, Kazoza Vision, Burundi). This is fixed in LPF 7.10.08.

34. If user repaid a loan from savings and then deleted the loan, the GL did not Balance anymore (BTrackerID 4208, Al-Halaal, Rwanda). This is fixed in LPF 7.10.08.

35. With group loans tracked at group level and group savings at member level, the Repay Arrears menu option created inconsistences between group and group member  savings and this option has been disabled (BTrackerID 4128, ID, Ghana). This is fixed in LPF 7.10.08.

36. Automatic Penalty calculation as a simple percentage created a bug. If at Loans Part 2, user would pick a product and then selected the option "Penalties calculated as a simple percentage" and then on the option group that appeared, (s)he did not select anything and saved. Then when (s)he went to calculate penalties and arrears for that product, the error appeared (BTrackerID 4139). This is fixed in LPF 7.10.08.

37. The fifth column at Retrieve Loans said "Membership date"�. This was incorrect and now shows "Application Date"� (BTrackerID 4162, Hekima, DR Congo). This is fixed in LPF 7.10.08.

38. The Approved Loans report generated an error ("CLoans has to be created with Select ... into Table,  BTrackerID 4199). This is fixed in LPF 7.10.08.

39. Column for Last Repayment date on the Loan Outstanding Balance Report-gave no data. This bug was corrected in 7.10.03 (see bugid 3784) but later versions were not updated (BTrackerID 4005). This is fixed in LPF 7.10.08.

40. The balances on the Outstanding Balances report were higher than the one on the Amounts due report if there were prepayments on a loan (BTrackerID 4199, The First Microfinance Agency, Kenya). This is fixed in LPF 7.10.08.

41. The Amounts Due Report has an option to print invoices. If the above option is activated, user can select a template (a Word document) that contains variables that will be replaced with values from LPF. For every line on the normal report, a separate invoice will be created as a file in the same folder as the template. From LPF, user can also set starting invoice number and invoice date (BTrackerID 4142, Indefund, Malawi). This is fixed in LPF 7.10.08.

42. Launching the Monitoring Report gave an error that lead to the termination of LPF (BTrackerID 4177). This is fixed in LPF 7.10.08.

43. There was a bug when trying to run the PMT report (BTrackerID 4176). This is fixed in LPF 7.10.08.

44. The Transactions per Voucher Number report now has different order/grouping options (Voucher Number (with sub-totals), Transaction code (no sub totals), Transaction date/time (with sub-totals per day), per Account and Transaction code (with sub-totals per account), Cost Centre and Transaction code (with sub-totals per cost centre, BTrackerID 4158, Hekima, DR Congo). This is fixed in LPF 7.10.08.

45. Menu Cash/Entry of Shares, Deposits, Loan Repayments bug when user clicked Next (BTrackerID 4126). This is fixed in LPF 7.10.08.

46. If user added a 2nd Cash Flow Report, user could only run the first one (BTrackerID 4159, Hekima, DR Congo). This is fixed in LPF 7.10.08.

47. Menu Tools, Checks on data entry, option "Due Interest unequal to Loan Amount" gave an error on clicking ok.. (BTrackerID 4178). This is fixed in LPF 7.10.08.

48. It was possible to enter a branch at Configuration/Banks, page 2, without selecting a bank first. This could create a branch that did not belong to any bank at all (BTrackerID 4196). This is fixed in LPF 7.10.08.

49. At menu Clients/Export Member to Excel, a checkbox is added to de-select the items in the Export column (BTrackerID 4075, Hope International, DR Congo). This is fixed in LPF 7.10.07.

50. When printing the Client Report for group members, the preview showed a different report from the print to PDF file (BTrackerID 4066, Hope International, DR Congo). This is fixed in LPF 7.10.07.

51. The Importation into Loan Performer now also works with the latest version of Excel (Office 2007) where files have an xlsx file format (BTrackerID 4065, Hope International, DR Congo). This is fixed in LPF 7.10.07.

52. The client's Identity Card - the one with the highest priority - has been added to the Savings Deposit and Withdrawal screens, Page 2 (with photo and signature, BTrackerID 4102, Hope International, DR Congo). This is done in LPF 7.10.07.

53. Added an extra savings interest method: interest compounded daily (BTrackerID 4029, EFFCO, South Africa). This is added in LPF 7.10.07.

54. Multiple Deposits did not show all accounts at ‘Define Item’ (BTrackerID 4064, Hope International, DR Congo). This is fixed in LPF 7.10.07.

55. If a group had a combination of savings products that were tracked at member and at group level and user made a transfer from a product that was tracked at member level to a product that was tracked at group level and then went to Clients, menu Groups and choose Group Members, clicked on a member and then choose to see the savings transactions of this member, LPF showed the group savings product as a product of this member with an incorrect balance. Also user could not set the end of membership because LPF said that client had a balance. The same thing happened when user wanted to transfer this member to another group (BTrackerID 4073, Hope International, DR Congo). This is fixed in LPF 7.10.07.

56. The rounding off of group loans and member loans was not consistent whether to round left or right or according to decimal places in Configuration/General. The left rounding at group member level was limited. If user had a setting of 2 decimals at Configuration/General, the group loan could not be rounded to 0 decimals. However if user set the number of decimals to zero, (s)he could enter the loan normally. Both options now give the same results (BTrackerID 4047, Hope International, DR Congo). This is fixed in LPF 7.10.07.

57. The following variables are added for the creation of the loan contracts at member level:
<Total Member Interest Amount>
<Total Member Repayable Amount>
<First Installment Amount Members>
<Last Installment Amount Members> (BTrackerID 4046, Hope International, DR Congo). This is done in LPF 7.10.07.

58. When printing group member loan contracts at loan application or disbursement, user input was required before the next member contract would be printed. With 40 members in a group this was a bit tedious. Now this is not necessary anymore (BTrackerID 4068, Hope International, DR Congo). This is fixed in LPF 7.10.07.

59. If an ID document is compulsory and user entered a loan guarantor at loan application and forgot to enter the ID Document, LPF closed the whole loan application and the user has to re-enter everything afresh (BTrackerID 4100, Hope International, DR Congo). This is fixed in LPF 7.10.07.

60. The savings GL account of a different savings product was credited when the loan was disbursed to the savings account (BTrackerID 4098, Socodevi, DR Congo). This is fixed in LPF 7.10.07.

61. Commission deducted at disbursement could lead to a GL difference because of rounding issues. For instance if you had a loan of 350 $ and commission of .75% to be deducted at disbursement with 2 decimals as standard setting, LPF showed both 347,37 and 347,38 on the receipt and booked debit and credit with 0.01 difference! (BTrackerID 4085, Hope International, DR Congo). This is fixed in LPF 7.10.07.

62. Printing of loan contracts for each group member at disbursement gave an Open Table error (BTrackerID 4113). This is fixed in LPF 7.10.07.

63. Declining Balance Loans produced negative balances if there were skipped dues and client later paid less interest than interest calculated (BTrackerID 4043). This is fixed in LPF 7.10.07.

64. With group loan repayments, if user selected as payment method "Direct to Bank" and then selected a bank other than the top most bank, it saved the top most bank, not the one (s)he selected (BTrackerID 4040, Bank of Barbedos, Barbedos). This is fixed in LPF 7.10.07.

65. On a large databases the entry of loan repayments was very slow (BTrackerID 4080, Swabhimaan, India). This is fixed in LPF 7.10.07.

66. The Update of Due Dates (below menu Disbursment) did not work for loans on declining balance. LPF said that "this option only works for FLAT RATE loans" (BTrackerID 4116, Socodevi, DR Congo). This is fixed in LPF 7.10.07.

67. Deletion of all repayments created a bug for loans on declining balance and the dues were not reset as they were before (BTrackerID 4041). This is fixed in LPF 7.10.07.

68. The Amounts to be Paid by Group Members for a loan at Loan Repayment could not be changed even if "Repayment Priorities Modifiable" is enabled, if on the "Which Loan Number" screen user selected a loan and went to the "Next" button using the "Tab" key (BTrackerID 4104, Vaksh, Tajikistan). This is fixed in LPF 7.10.07.

69. The Identity card - with the highest priority - has been added to the Loan Ledger Card and Loan Repayment Schedule (BTrackerID 4101, Hope Internation, DR Congo). This is fixed in LPF 7.10.07.

70. Group client codes and savings account numbers are added to the Collection Sheet (BTrackerID 4049, Hope International, DR Congo). This is done in LPF 7.10.07.

71. If a loan had been prepaid and closed, it would still show up in the Upcoming Maturity Loans report (though showing a principal balance of 0 and a negative interest balance, BTrackerID 4111, Viator Microcredit, Azerbaijan) This is fixed in LPF 7.10.07.

72. Report on customer's collateral did not show the value of the collateral, instead a value of 0 was displayed (BTrackerID 4096). This is fixed in LPF 7.10.07.

73. The Loan Cycles report for group members only showed the cycle number for the group, not the cycle number for the members (BTrackerID 4053, Hope International, DR Congo). This is fixed in LPF 7.10.07.

74. Chart of Accounts became corrupted if a whole group of accounts was moved to another header account (BTrackerID 4039). This is fixed in LPF 7.10.07.

75. Modification of transactions in the GL created a bug if the product was disabled ("Subscript out of defined range", BTrackerID 4091). This is fixed in LPF 7.10.07.

76. The feature to accrue interest on savings created a bug if user did not specify for which product this was to be done (BTrackerID 4084). This is fixed in LPF 7.10.07.

77. After saving (Adding) details of assets in "Asset Records", user was not able to make another entry of an asset unless (s)he cancelled and repeated the whole process again (i.e. Accounts/Assets/Asset Records). The information window showed "Branch has not been defined, please select" (BTrackerID 4038). This is fixed in LPF 7.10.07.

78. After entering the Debtors name at Debtors Registration and saving this, an error occured saying: "Function requires row or table buffering" (BTrackerID 4093, Sido, Tanzania). This is fixed in LPF 7.10.07.

79. Payment of Creditor's Invoices had an error after selecting the creditor ("Alias c_Invoice not found", BTrackerID 4087). This is fixed in LPF 7.10.07.

80. If user created a corporate database from branch databases where loans were tracked at member level, the consolidated database tracked loans at group level (BTrackerID 4085, Hope International, DR Congo). This is fixed in LPF 7.10.07.

81. At Tools/Controls the item Reset Loan Cycle now asks for a specific range of loan numbers. And if the loans are group loans, user can also indicate whether to update the loan cycle for the group (BTrackerID 4052, Hope International, DR Congo). This is fixed in LPF 7.10.07.

82. At Check Database under menu Tools, there is a check whether the total of principal (or interest) due for all installments is more than the loan (or interest) amount. This now also checks whether this is less than the loan (or interest) amount (BTrackerID 4117, Hekima, DR Congo). This is fixed in LPF 7.10.07.

83. Multiple users on 2x Application with remote desktop get file locking and sharing problems. This is for SQL Server Databases (BTrackerID 4020, REEF, Palestine). This is fixed in LPF 7.10.06. 

84. If a demo database was updated with a different branchcode, existing debtors/credits would become invisible (BTrackerID 3964, Sido, Tanzania). This is fixed in LPF 7.10.06. 

85. The cost centre was not correctly displayed when a client was retrieved. This was corrected for entry of individual clients (see bug ID 3597). Now it is also done only for group and business clients (BTrackerID 3930, Eclof, Kenya). This is fixed in LPF 7.10.06. 

86. In the "Modify Guarantors and Collateral" menu, the guarantor's names appear in the wrong order, making search difficult. The correct order is: Last Name, First Name, Middle Name (BTrackerID 3978, Vaksh, Tajikistan). This is fixed in LPF 7.10.06. 

87. The importation of shares transactions now allows transactions after the last transaction date, as long as no negative balance is created (BTrackerID 3932, K-Rep Fehda, Tanzania). This is fixed in LPF 7.10.06. 

88. LPF did not save the branch code in the General ledger if user made a deposit using menu Group Member Deposits. We have a patch available to correct existing data. Do contact us (BTrackerID 3983, Hekima, DR Congo). This is fixed in LPF 7.10.06. 

89. The calculation whether an account is dormant or not, was incorrect at Charges and Rewards. E.g. if an account has been dormant for a period of time and dormancy is broken on a certain date by entering a transaction and charges\rewards was run on the same date, while choosing only dormant accounts LPF still included this account (BTrackerID 3775). This is fixed in LPF 7.10.06. 

90. If client has an overdraft, the maximum overdraft amount and the available overdraft amount are added to the savers statement (BTrackerID 4015, EFFCO, South-Africa). This is added in LPF 7.10.06. 

91. Pass Book Printing with the option Print Range of Loans selected, an error occurred if user selected to Update Passbook, and then on the first Line No., a higher number was entered than the total no. of records shown and on the second Line No. user s/he would put a no. within the range of the records shown (Error: Record is out of range, BTrackerID 3999). This is fixed in LPF 7.10.06. 

92. The Personal Ledger Report for a group member gave an error (Table Repay not found, BTrackerID 3962). This is fixed in LPF 7.10.06. 

93. If rounding was set as a large negative (say -2 or -3), LPF incorrectly calculated dues for the last installment for group loans with member tracking so that the total of the dues for each instalment was not equal to the loan amount (BTrackerID 3995, Talanta, Uganda). This is fixed in LPF 7.10.06. 

94. An error occurred at loan application when user selected four monthly instalments (Incorrect value passed to function, BTrackerID 3987). This is fixed in LPF 7.10.06. 

95. Loan disbursement to member savings was incorrect if x% of disbursed amount had to go to loan guarantee savings and y% as commission. This is the same as bug 2700, but apparently this was only corrected at group level, but not at member level (BTrackerID 3992, Talanta, Uganda). This is fixed in LPF 7.10.06. 

96. When user made the last repayment for a loan on declining balance, only a partial amount was posted and the loan remained open with interest unpaid (BTrackerID 4021). This is fixed in LPF 7.10.06. 

97. The menu Group Member Repayments did not allow loan repayments from the savings account, whether this account was tracked at member level or not (BTrackerID 3937, Hekima, DR Congo). This is fixed in LPF 7.10.06. 

98. A penalty repayment was booked to the GL account of the loan commission. Also the description was incorrect (BTrackerID 3961, K-Rep Fehda, Kenya). This is fixed in LPF 7.10.06. 

99. The option "Freeze the loan" at Rescheduling was not working. For loans on declining balance, no interest should be charged after the date of freezing. This was not the case (BTrackerID 4023). This is fixed in LPF 7.10.06. 

100. If user selected "Direct to bank" at loan repayment and then selected a different bank account than the default account, LPF booked the payment to the default account instead of the selected bank account (BTrackerID 4026, Bank of Barbedos, Barbedos). This is fixed in LPF 7.10.06. 

101. Incorrect booking of interest on Time Deposits if monthly withdrawal to client's savings account. LPF credited the cash account as well as the savings account (BTrackerID 4025, Mecreco, DR Congo). This is fixed in LPF 7.10.06. 

102. If a Loan Disbursement was made to supplier, the supplier invoice remained open for payment after the loan had been disbursed. In addition, it was also possible to disburse more than the invoiced amount (BTrackerID 4016, EFFCO, South-Africa). This is fixed in LPF 7.10.06. 

103. If the repaid amount was less than the due amount for a loan bound to second currency, Loan Performer couldn't process the repayment. The message was: "Total amount of penalties, ... should be equal to the total amount paid" (BTrackerID 3989, Vaksh, Tajikistan). This is fixed in LPF 7.10.06. 

104. Loan Repayment using the Multipurpose entry screen was not possible when group savings were tracked differently. Now this is also possible if loans are tracked at member level and savings at group level (BTrackerID 3946).  This is fixed in LPF 7.10.06. 

105. A Group member’s Loan Repayments at Multi-Purpose Deposits did not post the amount set for all items (BTrackerID 3934).

106. Loan repayment using the Multi-Purpose Deposit screen created a bug (Variable MemNo not found, BTrackerID 3933). This is fixed in LPF 7.10.06. 

107. Multi-Purpose Deposit gave an error when using a bank transfer. A message "Transaction date not correct, must be between last transaction date and current login date and time." was displayed (BTrackerID 3941). This is fixed in LPF 7.10.06. 

108. The time displayed at write off was incorrect. It did not change according to the actual time of entry of the write off of a loan (BTrackerID 4003, Swabhimaan, India). This is fixed in LPF 7.10.06. 

109. The Column for Last Repayment Date on the Loan Outstanding Balances Report gave no data (BTracker 4005, Malanga, Mozambique). This is fixed in LPF 7.10.06. 

110. The Listing of Loan Repayments did not include loan repayments on the write-off date but before the write-off time, even if set (BTrackerID 4009, Swabhimaan, India). This is fixed in LPF 7.10.06. 

111. If a (balloon) loan has x instalments of only interest in arrears and the full loan amount is due on some future date, the Arrears Report included the loan amount in the Portfolio at Risk. However the Portfolio at Risk report did not. Now both of them show this loan (BTrackerID 3991). This is fixed in LPF 7.10.06. 

112. There were 3 formats of the Portfolio at Risk that did not tally with the report, e.g. number of days in arrears were missing (BTrackerID 3990). This is fixed in LPF 7.10.06. 

113. In the "Expected repayments of past and present dues" LPF showed loans that had been repaid (BTrackerID 3958). This is fixed in LPF 7.10.06. 

114. The "EXCHANGE RATE" in the report on Expected Repayments of Past and Present Dues did not show with the same number of decimals as at Support files/Exchange rates (BTrackerID 3682). This is fixed in LPF 7.10.06. 

115. The Transactions per Month report created a bug if user specified no date for which the report was to be run (BTrackerID 3931). This is fixed in LPF 7.10.06. 

116. If user selected to print account numbers on the Balance Sheet, LPF would print the account number of the last item in that group, not of the header account (BTrackerID 3993). This is fixed in LPF 7.10.06. 

117. It was impossible to link Invoices to Clients (BTrackerID 3938). This is fixed in LPF 7.10.06. 

118. If creditors (and also Debtor analysis codes) were used to classify invoices, LPF saved these codes incorrectly. It sometimes allowed the user to pick only the first Creditor analysis code and nothing else (BTrackerID 4012, EFFCO, South-Africa). This is fixed in LPF 7.10.06. 

119. Entry of Invoices received from Creditors created a bug (Array dimensions are invalid), especially if one line of the invoice from the supplier had a positive amount and the other line a negative amount (a discount, BTrackerID 4014, EFFCO, South-Africa). This is fixed in LPF 7.10.06. 

120. A Creditor's Payment gave an error (variable CASH is not found, BTrackerID 3944). This is fixed in LPF 7.10.06. 

121. Receipt from sales (Debtors receipts) gave a program error (Function requires row or table buffering, BTrackerID 3936). This is fixed in LPF 7.10.06. 

122. Printing Payment of Invoices Received gave an error (variable CASH is not found, BTrackerID 3939). This is fixed in LPF 7.10.06. 

123. Saving changes at System/Configuration/Loan Product Settings showed an error: Array dimensions are invalid (BTrackerID 3988). This is fixed in LPF 7.10.06. 

124. The Compulsory Savings Report had double entries for the same account and product if client had several savings products  (BTrackerID 3897, Five Talents, Uganda). This is fixed in LPF 7.10.05. 

125. Activating "Automatically modify due dates..." feature in "Set working days" lead to an incorrect number of instalments after disbursement of the loan (BTrackerID 3890). This is fixed in LPF 7.10.05. 

126. Automatic disbursements had an error (Variable 'MemID' is not found, BTrackerID 3916). This is fixed in LPF 7.10.05. 

127. It was impossible to disburse by Savings Transfer when Automatic Loan Disbursement was used for individual loans. LPF gave a message " The tracking methods for the loan and savings products are not compatible" BTrackerID 3893). This is fixed in LPF 7.10.05. 

128. Loan Repayment for individual loans had an error (Operator/Operand mismatch, BTrackerID 3919). This is fixed in LPF 7.10.05. 

129. If at configuration a guarantee was set for savings or shares, the loan application generated a bug (Variable "NReqVar" is not found, BTrackerID 3906). This is fixed in LPF 7.10.05. 

130. LPF did not check on shares balances required at automatic loan disbursement  (BTrackerID 3902). This is fixed in LPF 7.10.05. 

131. If user set a fixed amount as loan repayment for all group members at menu "Group Members Repayments" and saved this without modifying any amount, LPF posted a different amount from what the user set as payment (BTrackerID 3904). This is fixed in LPF 7.10.05. 

132. Loan Performer doubled interest repayments due for group members with loans on Declining balance when using Group Member Repayment module to enter repayments (BTrackerID 3895, Vaksh, Tajikistan). This is fixed in LPF 7.10.05. 

133. Group Member Repayments did not allow payment from Savings Account, whether this account is tracked at member level or not (BTrackerID 3878, Hekima, DR Congo). This is fixed in LPF 7.10.05. 

134. Editing an amount paid for a group loan with member tracking, did not change the value in the total paid column, consequently the user was unable to save the repayment (BTrackerID 3889, Hekima, DR Congo). This is fixed in LPF 7.10.05. 

135. The loan repayment for a group loan did not show the name of the member if "Member gets individual loan" was activated at configuration (BTrackerID 3887, Nachu, Kenya). This is fixed in LPF 7.10.05.  

136. Repay Arrears from Savings did not show all loans in arrears as in previous versions (BTrackerID 3884, CRAN, Ghana). This is fixed in LPF 7.10.05.  

137. Menu "Repay Arrears from Savings" did not recalculate interest for loans on declining balance (BTrackerID 3896). This is fixed in LPF 7.10.05. 

138. The calculation of provision on bad loans with option to show client names created a bug (SQL Column "Cluscode" not found, BTrackerID 3914. This is fixed in LPF 7.10.05. 

139. The disbursement disappeared from the loan ledger card if this was printed for multiple loans (BTrackerID 3905, Eclof, Kenya). This is fixed in LPF 7.10.05. 

140. If user went to Configuration/Loans Part 2, and selected any other option apart from the last one ("Penalties calculated on weekly basis"), the option "Penalty calculated for each late instalment" became visible. If s/he then activated this option, "Penalties should be calculated for a maximum of [] days after each late due" became visible.
If s/he then left the  "Penalty calculated for each late instalment" actif and changed to any other option from the first lot (apart from the last), the "Penalty calculated for each late instalment" became invisible, while the "Penalties should be calculated for a maximum of [] days after each late due" was still visible (BTrackerID 3885, Gret, Madagascar). This is fixed in LPF 7.10.05. 

141. The Year Closure in 7.10.04 created an incorrect transaction code, resulting in the user being unable to enter new transactions after the year closure (BTrackerID 3901). This is fixed in LPF 7.10.05. 

142. LPF booked provision to GL even if no start of financial year had been entered (BTrackerID 3899). This is fixed in LPF 7.10.05. 

143. The automatic write off of loans in arrears created a bug at the point of printing the report to the printer (BTrackerID 3898). This is fixed in LPF 7.10.05. 

144. The Name field was not wide enough on the Clients report, 2nd page (During a period), format no 2: New Clients and 3: Departing Clients (BTrackerID 3878, Swabhimaan, India). This is fixed in LPF 7.10.04. 

145. The comma between client's "<Last Name>, <First Name>" has been removed if user is logged in as a Russian user (BTrackerID 3738). This is fixed in LPF 7.10.04. 

146. Transferring Group Members when tracking Group Savings at Member level, did not give the correct balances (BTrackerID 3849). This is fixed in LPF 7.10.04. 

147. A Fixed Deposit Withdrawal by savings transfer for Group Clients should not be possible if Savings are tracked at member level (BTrackerID 3856). This is fixed in LPF 7.10.04. 

148. The repayment of loans from savings, did not work if some group members had outstanding loans and others did not (BTrackerID 3875, Hekima, DR Congo). This is fixed in LPF 7.10.04. 

149. Repay Arrears from Savings showed all the group members as having outstanding balances, even when some of the members did not have loans (BTrackerID 3874, Hekima, DR Congo). This is fixed in LPF 7.10.04.

150. User was unable to calculate penalties on arrears if penalty was set as a percentage (BTrackerID 3861, this was bug 3680 that was fixed in 7.10.02, Malanga, Mozambique). This is fixed in LPF 7.10.04.

151. Checkbox added to printing of Loan Ledger Card to cumulate penalty due instalments (BTrackerID 3866, Findev, Azerbaijan). This is fixed in LPF 7.10.04.

152. Reprint Repayment Schedule had an error (<Variable 'PENONWHAT'is not found>, BTrackerID 3873, Hekima, DR Congo). This is fixed in LPF 7.10.04.

153. The Loan Outstanding Balances Report with interest recalculated on loans on declining balance gave a different interest from the recalculated interest at loan repayment (BTrackerID 3848, Kapital Access, Uganda). This is fixed in LPF 7.10.04.

154. An irregular error was generated when the Performance Monitoring report was accessed ("LPF encountered a data type error"), (BTrackerID 3863, Malanga, Mozambique). This is fixed in LPF 7.10.04.

155. The Opening balances - after year closure - went into LPF with a wrong transaction code after year closure (BTrackerID 3852, Socodevi, DR Congo). This is fixed in LPF 7.10.04.

156. The reconcile Savings and Loans option under Accounts now has a selection for Individual, Group, Business or All clients (BTrackerID 3845, Emesco, Uganda). This is fixed in LPF 7.10.04.

157. LPF terminated when one accessed one of the Assets reports  (Assets Register or Depreciation) before accessing Purchases and Sales\Receipts from Sales (BTrackerID 3857). This is fixed in LPF 7.10.04.

158. LPF changed the language interface when user edited another user with another language setting (BTrackerID 3858). This is fixed in LPF 7.10.04.

159. Patch710 incorrectly updated the tables PaymCred or PaymDeb if these tables had records, leading to cheques disappearing (BTrackerID 3716, K-rep Fehda, Kenya). This is fixed in LPF 7.10.03. 

160.  If user starts up demo version, the intro screen shows how much of the records are used before user reaches the limit of a free - unlicensed - version (BTrackerID 3745). This is fixed in LPF 7.10.03. 

161.  If user deleted a newly entered group member, then immediately adds another member, an error is produced (Operator/Operand type mismatch (BTrackerID 3793). This is fixed in LPF 7.10.03. 

162.  Group members could be imported even if group member registration was before group registration date (BTrackerID 3757). This is fixed in LPF 7.10.03. 

163.  If the Signature or Photo folder referred to a folder that did not exist, user would get errors (Invalid path, BTrackerID 3826). This is fixed in LPF 7.10.03. 

164.  Added a new client report with Next of kin info (BTrackerID 3746, Swabhimaan, India). This is fixed in LPF 7.10.03. 

165.  LPF did not show the new balances of shares after transfer from one client to another (BTrackerID 3783). This is fixed in LPF 7.10.03. 

166.  Importation of Shares gave an error that the transaction date could not be before login date (BTrackerID 3749). This is fixed in LPF 7.10.03. 

167.  During modification of a savings transaction, it was possible for the user to modify a deposit to a lower value so that a subsequent withdrawal lead to a -ve balance (BTrackerID 3677, Malanga, Mozambique). This is fixed in LPF 7.10.03. 

168.  The Member Savings Transactions by Voucher Number Summary Report, instead of grouping the transactions by voucher number, LPF gave blank pages with only the titles at the top of the page (BTrackerID 3779). This is fixed in LPF 7.10.03. 

169.  Time Deposit Interest Rate was not read-only at Deposit Opening, if the selected Time Deposit product had equal min. and max. rates (BTrackerID 3741, Malanga, Mozambique). This is fixed in LPF 7.10.03. 

170.  A Bug (Unknown Member <OUGuarantors>) is reproduced when filtering on guarantors at loan application (BTrackerID 3759). This is fixed in LPF 7.10.03. 

171.  At importation of Loan applications the "Loan bound to second currency" option was not working. If later on user modified the application, this checkbox was not ticked (BTrackerID 3739). This is fixed in LPF 7.10.03. 

172.  If the variable "Percentage Interest in words" was used for generating contracts and the interest percentage has a decimal point, some completely irrelevant label appeared in the middle of the phrase (BTrackerID 3737). This is fixed in LPF 7.10.03. 

173.  Commas which came between client's names as it's done when users searches on client's name at Loan Repayment and in contracts have been removed if printed in Russian (BTrackerID 3738). This is fixed in LPF 7.10.03. 

174.  LPF took principal first before interest if a payment was made after the last instalment of a loan on declining balance with interest recalculated (BTrackerID 3794, Kapital Access, Uganda). This is fixed in LPF 7.10.03. 

175.  If user paid more than amount due on a loan linked to a foreign currency (s)he would get an error ("Total of penalties, commission, interest and principal should be equal to total amount paid.", BTrackerID 3772, MLO Vaksh, Tajikistan). This is fixed in LPF 7.10.03. 

176.  User could not enter repayments if the cost centre "Unknown" had been renamed and user had not assigned a cost center when entering the client (BTrackerID 3814). This is fixed in LPF 7.10.03. 

177.  The recalculation of interest during repayments for loans on declining balance now does not reset already calculated amounts (BTrackerID 3839, Kapital Access, Uganda). This is fixed in LPF 7.10.03. 

178.  In case of loans on declining balance and interest calculation in days, when user choose to close the loan without recalculating interest, all the interest due after the date of closure of the loan remained outstanding on the ledger card and on the outstanding balances report (BTrackerID 3824, Pamoja, Kenya). This is fixed in LPF 7.10.03. 

179. The group member repayments entry screen created an error with receipt printing activated and the receipt format was the "Fonzoke receipt" (BTrackerID 3828). This is fixed in LPF 7.10.03. 

180. Repay Arrears from Client's Savings had an error (Column <cName> not found) that lead to the termination of LPF (BTrackerID 3709). This is fixed in LPF 7.10.03. 

181. The deletion of a penalty was not working (BTrackerID 3770). This is fixed in LPF 7.10.03. 

182. Reschedule a loan with an interest that has been recalculated, after adding an Additional number of instalments and clicking on the Fill Repayment dues button, an error pops up and user can not proceed with any transactions (BTrackerID 3766). This is fixed in LPF 7.10.03. 

183. The rescheduling of a loan now has the option of calculating the additional interest on the outstanding balance instead of the loan amount in case user adds on extra instalments on flat rate loans (BTrackerID 3838, Kapital Access, Uganda). This is fixed in LPF 7.10.03. 

184. Loan Outstanding Balance Report with recalculated interests on loans on declining balance gave an interest far different from the recalculated interest at loan repayment (BTrackerID 3822). This is fixed in LPF 7.10.03. 

185. The Pending Disbursement Report with option Summary, omitted the total (BTrackerID 3729). This is fixed in LPF 7.10.03. 

186. The Reprint Repayment Schedule report gave an error if printed for a written off loan (Variable <penOnWhat> is not found. BTrackerID 3733). This is fixed in LPF 7.10.03. 

187. The report of Expected repayments of past and present dues showed prepaid amounts as negative amounts of principal in arrears (BTrackerID 3735). This is fixed in LPF 7.10.03. 

188. One of the reports on Outstanding Loans has a column with the last repayment date (BTrackerID 3784, Kapital Access, Uganda). This is fixed in LPF 7.10.03.