| |
1. The lpfdll versioning has been included to prevent users from running an old DLL and getting runtime errors (BTrackerID 4332).
2. The conversion of a Foxpro database to SQL Server automatically set a closing date for the loan fund under Configuration/Funds (BTrackerID 4140). This is fixed in a new binarytochar.exe file (click to download).
3. If Identity Card numbers are unique, it was impossible to update someone's ID card number with a different Issue date or place. When clicking the Update button, LPF said "Someone has the same ID number" (BTrackerID 4364).
4. Group member document ID numbers were only unique for members in the same group and not members in other groups (BTrackerID 4312, Beit-el-Mal, Mauretanie).
5. Importation of individual clients or group members with ID documents was not possible. LPF said that the ID Document code did not exist (while it did), (BTrackerID 4295, see also 4195, Fonkoze, Haiti).
6. The report on clients was not correct, the total for all clients was not equal to clients with outstanding balances and those without (BTrackerID 4263).
7. When logged in as Guest, the Report on Clients, produced an error (BTrackerID 4185).
8. The Personal Ledger Balances report gave an error ("CLOANS must be created with SELECT .. INTO TABLE", BTrackerID 4299, eGroup Agir, Haiti). to top 
9. Shares sold by cheque were doubled in cases of a bounced cheque for buying shares (BTrackerID 4376).
10. The importation of shares was not allowed if the account numbers had more than 6 digits (BTrackerID 4324, Coopec Nyawera, DR Congo).
11. With Receipt Printing activated, a savings withdrawal did not refresh the withdrawal form after saving and printing a receipt (BTrackerID 4384).
12. A member in a group could withdraw the balance deposited by cheque before the cheque was cleared (BTrackerID 4370).
13. Savings deposited by cheque could be withdrawn prior to the cheque clearing date, as long the cheque was cleared (BTrackerID 4358).
14. This is the same with buying of shares from savings before the cheque clearing date, see bug 4358 (BTrackerID 4378).
15. At closure of a savings account, LPF did not check if the client has any uncleared cheques (BTrackerID 4375).
16. LPF asked for commission on local cheques even when commission on local cheques was set to zero at System/Configuration/Saving. This happened only if commission on other cheques was set (BTrackerID 4380) to top
17. It was possible to make a savings transfer from a clients account to a group members account while the group member had ended membership and the transfer date was after the end of membership date (BTrackerID 4285, Fonkoze, Haiti).
18. The Savers statement had an error, if user selected any of the last 3 report output formats, the combo box for the output format got misplaced. (BTrackerID 4271).
19. The Savings Balances report has a format option with Group Account, Member Number and Member Name (BTrackerID 4297, Fonkoze, Haiti). to top
20. A page has been added at entry of group savings withdrawal that shows signatories' photos and signatures (BTrackerID 4276, Al-Halaal, Rwanda).
21. If user entered a Time Deposit and before the expiry date withdrew the TD and ticked the checkbox "No interest", LPF booked the not-paid interest as income and created a booking that was not balancing (BTrackerID 4323).
22. The withdrawal of Time Deposits was possible even if the deposited cheque had not cleared (BTrackerID 4349).
23. The Time Deposit Report for TDs opened in the period did not show all the outstanding time deposits. If a TD was closed in the period, the report did not show this. A checkbox is added that makes it possible to include all TDs (BTrackerID 4264).
24. The Closed Time-Deposits report now shows what is principal and what is interest. So far the report gave the total paid, not the separate amounts (BTrackerID 4367, Fonkoze, Haiti).
25. The recalculation of interest on loans with declining balance now has a feature to limit the past period for calculating interest (BTrackerID 4356, Indefund, Malawi). to top
26. The interest calculation of loans with declining balance did not produce the expected interest in case there were several partial payments of interest only (BTrackerID 4335, Hekima, DR Congo).
27. Total VAT is added as a variable to the loan contracts (BTrackerID 4359, Aspire, Mexico).
28. First and Last installment date were not printed on loan contract (BTrackerID 4338, Paidek, DR Congo).
29. Repaying a loan from savings is now possible if the group loan is at member level and the savings are tracked at group level (BTrackerID 4129).
30. The importation of loan disbursements by cheque created a bug (BTrackerID 4320, Mukono Teachers, Uganda).
31. The importation of partial disbursement was incorrectly booked (BTrackerID 4279).
32. The importation of Loan repayments by cheque created an error (BTrackerID 4319, Mukono Teachers, Uganda).
33. When making a group loan repayment for a loan and "Savings Transfer" was selected, user would get a message saying 'There's no savings balance', although the group members had savings balances (BTrackerID 4318). to top
34. The transaction number given at Loan Repayment could be different from the one saved in the GL (BTrackerID 4314).
35. Generating Loan Contracts at menu Portfolio Reports/Generate Loan Contracts created an error ("A required file is not available in the database", BTrackerID 4305).
36. Rescheduling a loan on a SQL Server database caused the first installment for the loan to disappear. This happened when user rescheduled the loan and just changed the interest amount for one installment due and then saved (BTrackerID 4254).
37. The Portfolio At Risk Report showed different dates on the screen and the report (BTrackerID 4386, The First Microfinance Agency, Kenya).
38. The Portfolio Report in a summary format created a bug: "A required file is not available in the database" (BTrackerID 4331, Leap, Liberia).
39. If there were prepayments, The Portfolio At Risk Report showed negatives and was not consistent with the Ageing and Arrears Reports (BTrackerID 4322, Swabhimaan, India). to top
40. The Portfolio At Risk report did not show proper summaries when grouped by credit officer (BTrackerID 4280, Five Talents).
41. The Provision report did not show all selection criteria that user entered in the report header (BTrackerID 4283).
42. The summary report of the Outstanding Balances Report per product printed the last column for each loan in detail (BTrackerID 4262).
43. The 'Principal paid in advance', 'Principal paid and due' and 'Principal paid and past due' rows of the Indicators Report were not correct (BTrackerID 4257, Five Talents, Uganda).
44. Penalties could be calculated only once for a given period. If user had removed some clients from the calculation, (s)he could not calculate penalties again for the same period (BTrackerID 4373, Aspire, Mexico).
45. The entry/update of Loan and Client's Savings Account numbers as analysis code is now possible in the GL (BTrackerID 4377, Hekima, DR Congo).
46. Three more variables are added at Invoicing (Principal Due, Interest Due and Penalty due) at the Amounts Due Report. So far it only showed "Amount Due" which is a total of Principal + Interest due (BTrackerID 4352, Indefund, Malawi).
47. Generating Invoices at the Amounts Due Report when all Amount Dues were selected, gave an error that forced user to back up (BTrackerID 4302). to top
48. At Accounts/Reconcile Savings and Loan transactions, if user selected Business Accounts, after first having selected Individual or Group Accounts and having run the report, LPF showed the same report as for individual or group accounts (BTrackerID 4381).
49. Multi-purpose cash deposits left out the provision for entering savings, after selecting a client, only the loan repayments appeared (BTrackerID 4251).
50. The Breakdown per Account report produced an incorrect summary report for accounts having more than 6,000 transactions (BTrackerID 4328, KRep-Fehda, Kenya).
51. A selection box is added for client type (Individual , Group, Buss) at 2nd page of the Reconcile Savings and Loans menu (BTrackerID 4344, Coopec Nyawera, DR Congo).
52. The menu "Reconcile Savings and Loan Transactions", the option "Reconcile Loans" option for all accounts was not equal to the total of Individual and Group Accounts. (BTrackerID 4334).
53. If at "Reconcile Savings and Loan Transactions", user choose savings balances for Businesses, (s)he would get the same for groups, not for business accounts (BTrackerID 4334). to top
54. The Reconcile Savings gave an incorrect balance for accounts with more than 1 transaction on the same day if the last transaction was a deposit that was entered first and a withdrawal entered later but with a computer timestamp that is earlier, (BTrackerID 4334).
55. An Update button has been added on page 2 at Asset Registration (BTrackerID 4350, Al-Halaal, Rwanda).
56. It is now possible to delete an asset wrongly registered at Assets registration as long as no financial transactions have been entered in the GL (BTrackerID 4313, EFFCO, RSA).
57. The option "Additional Checks" at menu Tools/Check Database now also checks for 1. Transactions posted on the Outstanding Loans account that are not found in the disbursement, the loan repayment or the deleted disbursements/loans/loan repayments table and 2. Transactions in the sub-ledgers (disbursement, the loan repayment or the deleted disbursements/loans/loan repayments) that are not in the general ledger table (BTrackerID 4345).
58. Data entry checks at Tools/Check Database, option "Savings Accounts without transactions" did not function as expected. Even if there was an account without transactions LPF said that all savings accounts have transactions (BTrackerID 4367).
59. The item "Voucher" at System/Configuration/Accounting/Order Day Closure Report was missing in the French version (BTrackerID 4343). to top
60. At System\Configuration\Funds, if user modified a Fund contribution by cheque before the cheque was cleared, LPF displayed an error message ("SQL Column BName is not found", BTrackerID 4382).
61. Error at System\Configuration\Value Added Tax "Column Trancode is not found" (BTrackerID 4354).
62. If at System\Receipt Log, user selected the mode of payment LPF displaid an error ("Data type mismatch", BTrackerID 4353).
63. If user installed a license into an unlicensed database, the 'Branches' field in the Users table was not updated (BTrackerID 4131, Paidek, DR Congo).
64. 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).
65. Installation of LPF in another language other than English gave an error ("Uniqueness of index Langname is violated", BTrackerID 4168, Al-Halaal, Rwanda). to top
66. Error at menu Clients/Individuals, Groups and Business clients ("Property
not found", BTrackerID 4175).
67. Importation of Individual Clients without ID documents was impossible even when ID documents were not mandatory (BTrackerID 4195).
68. Error at guarantors when user clicked on the filter button and then on the print button (BTrackerID 4137).
69. 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).
70. The Report on client ID documents did not show the selection made (BTrackerID 4193).
71. Receipt printing at the sale of shares is added (BTrackerID 4200, Mtoni, Tanzania).
72. 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).
73. User can now also search by co-account holder when making deposits (BTrackerID 4173, Malanga, Mozambique).
74. Savings deposit and withdrawal slips now show the client's reference number if not empty (BTrackerID 4150, Al-Halaal, Rwanda).
75. A new receipt format (AL-Halaal) is added for savings deposits and withdrawals (BTrackerID 4172, Al-Halaal, Rwanda).
76. Printing of a range of savers statements is added (from account: ... to account: ..., BTrackerID 4134, Ned-Consultants, Nigeria).
77. A format with name of the client is added to the Savings Tillsheet (BTrackerID 4166, Al-Halaal, Rwanda).
78. Order options added for Savings Tillsheet (options: day-time, transaction code, voucher, BTrackerID 4165, Al-Halaal, Rwanda).
79. If receipts were saved to PDF into a given folder, the deposits were saved but not the withdrawals (BTrackerID 4202, Mtoni, Tanzania). to top
80. LPF allowed a withdrawal from the client savings account even if there were un-cleared cheques (BTrackerID 4198, Al-Halaal, Rwanda).
81. Importation of savings transfers for the same client on the same day on the same account gave wrong balances (BTrackerID 4174, Al-Halaal, Rwanda).
82. 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).
83. The Importation of Savings transactions without any of the transactions being a withdrawal, created a run time error (BTrackerID 4180).
84. The savings till sheet has an option to print both the Reference number and the Client Name (BTrackerID 4179, Al-Halaal, Rwanda).
85. The Group Member Savers Statement gave incorrect balances if run for different periods (BTrackerID 4218, Buusaa Gonofa, Ethiopia).
86. User can import Time Deposits (BTrackerID 4188, Coopec-Nyawera, DR Congo).
87. Added
and
to loan contract variables (BTrackerID 4154, Mecap, Senegal). to top
88. 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).
89. 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).
90. Deleting a Loan Repayment without selecting a loan, deleted all repayments in the database (BTrackerID 4148, Kazoza Vision, Burundi).
91. The deletion of loan disbursement created a bug in selected databases (Variable
is not found, BTrackerID 4123, Bancs Microfinance, Uganda).
92. Importation of Loan Disbursement with commission deducted gave an error ("Property TCode not found", BTrackerID 4210, Habitat, Costa Rica).
93. Importing loan repayments by savings transfer gave an error about savings product not being found (BTrackerID 4214, Habitat, Costa Rica). to top
94. The Importation of loan repayments with Mode = 4 (direct to bank) was not possible (BTrackerID 4215, Habitat, Costa Rica, Kazoza Vision, Burundi).
95. If user repaid a loan from savings and then deleted the loan, the GL did not Balance anymore (BTrackerID 4208, Al-Halaal, Rwanda).
96. 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).
97. 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).
98. The fifth column at Retrieve Loans said "Membership date". This was incorrect and now shows "Application Date" (BTrackerID 4162, Hekima, DR Congo).
99. The Approved Loans report generated an error ("CLoans has to be created with Select ... into Table, BTrackerID 4199).
100. 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). to top
101. 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).
102. 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).
103. Launching the Monitoring Report gave an error that lead to the termination of LPF (BTrackerID 4177).
104. There was a bug when trying to run the PMT report (BTrackerID 4176). to top
105. 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).
106. Menu Cash/Entry of Shares, Deposits, Loan Repayments bug when user clicked Next (BTrackerID 4126).
107. If user added a 2nd Cash Flow Report, user could only run the first one (BTrackerID 4159, Hekima, DR Congo).
108. Menu Tools, Checks on data entry, option "Due Interest unequal to Loan Amount" gave an error on clicking ok.. (BTrackerID 4178).
109. 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).
110. 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). to top
111. 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).
112. 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).
113. 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).
114. Added an extra savings interest method: interest compounded daily (BTrackerID 4029, EFFCO, South Africa).
115. Multiple Deposits did not show all accounts at Define Item (BTrackerID 4064, Hope International, DR Congo).
116. 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). to top
117. 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).
118. The following variables are added for the creation of the loan contracts at member level:
(BTrackerID 4046, Hope International, DR Congo). to top
119. 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).
120. 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).
121. 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).
122. 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).
123. Printing of loan contracts for each group member at disbursement gave an Open Table error (BTrackerID 4113).
124. Declining Balance Loans produced negative balances if there were skipped dues and client later paid less interest than interest calculated (BTrackerID 4043). to top
125. 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).
126. On a large databases the entry of loan repayments was very slow (BTrackerID 4080, Swabhimaan, India).
127. 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).
128. Deletion of all repayments created a bug for loans on declining balance and the dues were not reset as they were before (BTrackerID 4041).
129. 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). to top
130. 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).
131. Group client codes and savings account numbers are added to the Collection Sheet (BTrackerID 4049, Hope International, DR Congo).
132. 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)
133. Report on customer's collateral did not show the value of the collateral, instead a value of 0 was displayed (BTrackerID 4096).
134. 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).
135. Chart of Accounts became corrupted if a whole group of accounts was moved to another header account (BTrackerID 4039).
136. Modification of transactions in the GL created a bug if the product was disabled ("Subscript out of defined range", BTrackerID 4091).
137. 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). to top
138. 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).
139. 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).
140. Payment of Creditor's Invoices had an error after selecting the creditor ("Alias c_Invoice not found", BTrackerID 4087).
141. 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). to top
142. 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).
143. 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).
144. Multiple users on 2x Application with remote desktop get file locking and sharing problems. This is for SQL Server Databases (BTrackerID 4020, REEF, Palestine).
145. If a demo database was updated with a different branchcode, existing debtors/credits would become invisible (BTrackerID 3964, Sido, Tanzania). to top
146. 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).
147. 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).
148. 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).
149. 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). to top
150. 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).
151. 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).
152. 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). to top
153. The Personal Ledger Report for a group member gave an error (Table Repay not found, BTrackerID 3962).
154. 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).
155. An error occurred at loan application when user selected four monthly instalments (Incorrect value passed to function, BTrackerID 3987).
156. 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). to top
157. 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).
158. 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).
159. A penalty repayment was booked to the GL account of the loan commission. Also the description was incorrect (BTrackerID 3961, K-Rep Fehda, Kenya).
160. 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). to top
161. 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).
162. 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).
163. 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).
164. 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). to top
165. 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).
166. A Group members Loan Repayments at Multi-Purpose Deposits did not post the amount set for all items (BTrackerID 3934).
167. Loan repayment using the Multi-Purpose Deposit screen created a bug (Variable MemNo not found, BTrackerID 3933).
168. 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).
169. 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). to top
170. The Column for Last Repayment Date on the Loan Outstanding Balances Report gave no data (BTracker 4005, Malanga, Mozambique).
171. 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).
172. 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).
173. 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).
174. In the "Expected repayments of past and present dues" LPF showed loans that had been repaid (BTrackerID 3958).
175. 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). to top
176. The Transactions per Month report created a bug if user specified no date for which the report was to be run (BTrackerID 3931).
177. 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).
178. It was impossible to link Invoices to Clients (BTrackerID 3938).
179. 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).
180. 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).
181. A Creditor's Payment gave an error (variable CASH is not found, BTrackerID 3944).
182. Receipt from sales (Debtors receipts) gave a program error (Function requires row or table buffering, BTrackerID 3936).
183. Printing Payment of Invoices Received gave an error (variable CASH is not found, BTrackerID 3939).
184. Saving changes at System/Configuration/Loan Product Settings showed an error: Array dimensions are invalid (BTrackerID 3988).
185. The Compulsory Savings Report had double entries for the same account and product if client had several savings products (BTrackerID 3897, Five Talents, Uganda). to top
186. Activating "Automatically modify due dates..." feature in "Set working days" lead to an incorrect number of instalments after disbursement of the loan (BTrackerID 3890).
187. Automatic disbursements had an error (Variable 'MemID' is not found, BTrackerID 3916).
188. 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).
189. Loan Repayment for individual loans had an error (Operator/Operand mismatch, BTrackerID 3919).
190. If at configuration a guarantee was set for savings or shares, the loan application generated a bug (Variable "NReqVar" is not found, BTrackerID 3906). to top
191. LPF did not check on shares balances required at automatic loan disbursement (BTrackerID 3902).
192. 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).
193. 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).
194. 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).
195. 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).
196. 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). to top
197. Repay Arrears from Savings did not show all loans in arrears as in previous versions (BTrackerID 3884, CRAN, Ghana).
198. Menu "Repay Arrears from Savings" did not recalculate interest for loans on declining balance (BTrackerID 3896).
199. The calculation of provision on bad loans with option to show client names created a bug (SQL Column "Cluscode" not found, BTrackerID 3914.
200. The disbursement disappeared from the loan ledger card if this was printed for multiple loans (BTrackerID 3905, Eclof, Kenya).
201. 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). to top
202. 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).
203. LPF booked provision to GL even if no start of financial year had been entered (BTrackerID 3899).
204. The automatic write off of loans in arrears created a bug at the point of printing the report to the printer (BTrackerID 3898).
205. 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).
206. The comma between client's "
,
" has been removed if user is logged in as a Russian user (BTrackerID 3738).
207. Transferring Group Members when tracking Group Savings at Member level, did not give the correct balances (BTrackerID 3849).
208. A Fixed Deposit Withdrawal by savings transfer for Group Clients should not be possible if Savings are tracked at member level (BTrackerID 3856). to top
209. 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).
210. 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).
211. 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).
212. Checkbox added to printing of Loan Ledger Card to cumulate penalty due instalments (BTrackerID 3866, Findev, Azerbaijan).
213. Reprint Repayment Schedule had an error (
, BTrackerID 3873, Hekima, DR Congo). to top
214. 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).
215. An irregular error was generated when the Performance Monitoring report was accessed ("LPF encountered a data type error"), (BTrackerID 3863, Malanga, Mozambique).
216. The Opening balances - after year closure - went into LPF with a wrong transaction code after year closure (BTrackerID 3852, Socodevi, DR Congo).
217. The reconcile Savings and Loans option under Accounts now has a selection for Individual, Group, Business or All clients (BTrackerID 3845, Emesco, Uganda).
218. LPF terminated when one accessed one of the Assets reports (Assets Register or Depreciation) before accessing Purchases and Sales\Receipts from Sales (BTrackerID 3857). to top
219. LPF changed the language interface when user edited another user with another language setting (BTrackerID 3858).
220. Patch710 incorrectly updated the tables PaymCred or PaymDeb if these tables had records, leading to cheques disappearing (BTrackerID 3716, K-rep Fehda, Kenya).
221. 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).
222. If user deleted a newly entered group member, then immediately adds another member, an error is produced (Operator/Operand type mismatch (BTrackerID 3793).
223. Group members could be imported even if group member registration was before group registration date (BTrackerID 3757).
224. If the Signature or Photo folder referred to a folder that did not exist, user would get errors (Invalid path, BTrackerID 3826).
225. Added a new client report with Next of kin info (BTrackerID 3746, Swabhimaan, India).
226. LPF did not show the new balances of shares after transfer from one client to another (BTrackerID 3783).
227. Importation of Shares gave an error that the transaction date could not be before login date (BTrackerID 3749). to top
228. 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).
229. 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).
230. 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).
231. A Bug (Unknown Member
) is reproduced when filtering on guarantors at loan application (BTrackerID 3759).
232. 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).
233. 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). to top
234. 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).
235. 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).
236. 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).
237. 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). to top
238. The recalculation of interest during repayments for loans on declining balance now does not reset already calculated amounts (BTrackerID 3839, Kapital Access, Uganda).
239. 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).
240.The group member repayments entry screen created an error with receipt printing activated and the receipt format was the "Fonzoke receipt" (BTrackerID 3828).
241.Repay Arrears from Client's Savings had an error (Column
not found) that lead to the termination of LPF (BTrackerID 3709).
242. The deletion of a penalty was not working (BTrackerID 3770). to top
243.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).
244.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).
245. 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).
246. The Pending Disbursement Report with option Summary, omitted the total (BTrackerID 3729). to top
247.The Reprint Repayment Schedule report gave an error if printed for a written off loan (Variable
is not found. BTrackerID 3733).
248.The report of Expected repayments of past and present dues showed prepaid amounts as negative amounts of principal in arrears (BTrackerID 3735).
249. One of the reports on Outstanding Loans has a column with the last repayment date (BTrackerID 3784, Kapital Access, Uganda).
250.The report on loans transferred from one credit officer to another now also shows the client name (BTrackerID 3731).
251. If at entry of cash expenses, user did not enter an amount but just saved, LPF gave an error (Error
not found, BTrackerID 2129).
252.Deposits for multiple clients could not save if user clicked the Update button (by mistake) followed by the Add button (BTrackerID 3715).
253.User was able to enter an account as Income and move it to a balance sheet account or vice versa, this violating the rule that sub-accounts have to be of the same type as the main account (BTrackerID 3751). to top
254.With the French BCEAO Chart of Accounts, the user could not create Passive accounts starting with acc no. 1, nor can (s)he import these (BTrackerID 3734).
255.It at menu "Recalculate Accrued Interest and Penalties", user ticked "Accrued Interest on Loans only" an error was produced ("Open tables in database", BTrackerID 3740).
256.If at the same menu user selected "Accrue Penalties on Loans", LPF would show an error SQL column
not found (BTrackerID 3790).
257. The Export of Transactions by Voucher number now also includes all analysis codes of the general ledger (BTrackerID 3754, Hekima, DR Congo.
258.If a debtor or creditor was linked to a "Passive" account, LPF would show a different account when retrieving the debtor/creditor (BTrackerID 3755, Hekima, DR Congo).
259. User can now select whether to print the Balance Sheet with or without account numbers (BTrackerID 3756, Hekima, DR Congo).
260.User is now able to set the width of columns for passbook printing (the minimum field width values have been removed, BTrackerID 3730, Coocreditto, Ecuador). to top
261.If the chart of accounts had accounts like 1520 And 1520a and one of the accounts was used to link principle outstanding for a loan product, it was not possible to enter a repayment (BTrackerID 3753, Hekima, DR Congo).
262.If user made a selection of a particular, cleared cheque, the particulars such as transaction no., payment date, payment type etc. do not change apart from the cheque number. This did not occur if the cheque was cleared (BTrackerID 3787).
263.If receipt were to be saved and user had specified a folder that did not exist, LPF hangs when printing receipts (BTrackerID 3833).
264.If user had defined bank accounts, then switched the chart of accounts to BCEAO, he got an error 'bname does not exist' (BTrackerID 3750).
265. Guest user can be disabled and password can be set for Guest user (BTrackerID 3776, Malanga, Mozambique).
266. User was not able to end registration of a client if the client had an outstanding loan that was written-off ( BTrackerID 3702, Hope Micro, Sierra Leone). to top
267. Error when updating an existing loan guarantor ("Property NGUARNO is not a method or event", BTrackerID 3713).
268. It was not possible to import Clients who had an ID document with an empty expiry date (BTrackerID 3684).
269. When user closed the cheques window when buying/selling Shares by cheque, an error occurred ("Operator/Operand type mismatch", BTrackerID 3722).
270. The Time Deposit amount, interest or period now become read-only if at configuration the min. and max. values are equal ( BTrackerID 3708, MBM, Mozambique).
271. It was not possible to withdraw a Time-Deposit without paying interest ( BTrackerID 3695, MBM, Mozambique).
272. If user chose to renew a time deposit when matured, (s) he could not transfer the interest to a savings account ( BTrackerID 3674, MBM, Mozambique).
273. The modification of savings transactions for group savings with member tracking was not possible if you had two consecutive transactions, one of which was a withdrawal ( BTrackerID 3670). to top
274. The Period Balances report for Savings, if run for a large amount of data, could run into the limitations of an array and user would get a message like "Found 11759 records, this program can process up to 5416 records only" ( BTrackerID 3714).
275. Receipt for disbursement was incorrect if interest was deducted at disbursement ( BTrackerID 3658, Microstart, Burkina Faso).
276. Error at Repay Arrears from Client's Savings has an error ("Column CNAME not found", BTrackerID 3709).
277. The repay arrears from savings feature now also shows the client's name, not just Loan numbers and savings account numbers ( BTrackerID 3675, MBM, Mozambique).
278. Error at Delete Repayments (One Group Member's Repayment only): When user selected "One Group Member's Repayment Only", (s)he would get a message "There are no repayments to delete". When user went ahead and entered a reason for deleting a group member's repayment, user was prompted to first select a group member's name first, but there was no option for selecting a group member's name (BTrackerID 3718).
279. Importation of disbursements for loans with interest deducted at disbursement crashed ( BTrackerID 3720).
280. If at importation of loan repayments, any of the loans in the import file was not found in the database, LPF reported that all of them are non existing, including the one(s) that exist ( BTrackerID 3721). to top
281. Importation of loan repayments for individual clients duplicated the first repayments and caused negative balances ( BTrackerID 3719, The First Microfinance Agency, Kenya).
282. User was unable to calculate penalties on arrears if penalty was set as a percentage ( BTrackerID 3680, MBM, Mozambique).
283. The Automatic calculation of penalties gave output for group loans if user asked for the computation of penalties for individual clients ( BTrackerID 3671, MBM, Mozambique).
284. The penalty percentage for arrears has been extended to more than 999% ( BTrackerID 3676, MBM, Mozambique).
285. The "EXCHANGE RATE" in the report on Expected Repayments of Past and Present Dues did not shown with the same number of decimals as at Support files/Exchange rates ( BTrackerID 3682).
286. The report on Amounts Due had an error that lead to the termination of LPF if user activated "Recalculate interests for loans on declining balance" (BTrackerID 3707).
287. User was able to enter a transaction on the last day of a closed month even though according to the configuration, this was not allowed ( BTrackerID 3701, MBM, Mozambique). to top
288. If user had not properly linked an item to a GL account, the posting of the transaction was refused as the account was non existent in the chart of accounts, but the user was not informed which was the account that was not found (BTrackerID 3706, MBM, Mozambique).
289. If user activated the option "Recalculate interest for loans on declining balance" at the Accrue Interest menu, ran the report, but then decided not to update the GL accounts, the interest remained recalculated (BTrackerID 2276).
290. Reconcile Savings and Loan Balances-Loans Per Day had an error ("Variable NRUNS not found") if on Page 1 user selected an option higher than 4 and then moved to page 3 and ran the report from page 3 (BTrackerID 3705).
291. Bug when enlarging Cheque Clearing window at menu System ( BTrackerID 3699).
292. If after importing a chart of accounts at Configuration/Accounts page 2, the user clicked Save on page 1, a buffering error occurred (BTrackerID 3700, MBM, Mozambique).
293. Opening of the Balance Sheet in a Corporate database generated an error ("Selects are not Union Compatible", BTrackerID 3685).
294. If user had more than one Time-deposit product, at Configuration/Time-Deposits, page 2 did not refresh if user changed from one product to the other (BTrackerID 393, MBM, Mozambique). to top
295. When user logged out via System/Login-Logout and logged into another database, not all variables were refreshed. For instance the loan funds at loan application would show the funds of the previous database (BTrackerID 3691).
296. LPF recalculated interest even if at repayment user had indicated not to do so (with setting "User can decide whether to recalculate interest at repayment for loans on declining balance", BTrackerID 3672, MBM, Mozambique).
297. If at Asset Register user deactivated first asset, all other assets could not be deactivated (BTrackerID 3661).
298. If user modified a savings transaction, put the amount at zero and when asked to delete this transaction, cancelled, LPF left the user in a non-committed transaction, causing problems elsewhere (BTracker 3640).
299. If user modified a "Multiple Deposits" transaction by cheque and changed the amount of one of the depositors, the un-cleared cheque amount would have to either increase or decrease according to the changes made, but it did not (BTracker 3590).
300. If user pressed the Cancel button at withdrawal of a Time-Deposit, an error was generated ("Cannot access the selected table", BTracker 3601). to top
301. The reprint of the interest report on savings could not be run if the interest method was not on Running or Monthly Minimum balances (BTracker 3639).
302. If a loan with member tracking was disbursed to the group member's savings accounts and any fees were deducted at disbursement, LPF would not deduct those fees when transferring the member loan amounts (BTracker 3642).
303. An error was generated at loan disbursement ("SQL: Column 'PRINCDUE' is not found"), if the parameter "Dis-allow disbursement if partner has outstanding loan" was activated at Configuration/Loans part 1 (BTracker 3514).
304. Disbursement date could be earlier than approval date if disbursements were done automatically (BTracker 3643).
305. At Automatic Loan Disbursement when using option "Update due dates with the difference..." an error "Variable TSTART not found" occurred (BTracker 3651).
306. Loan repayments did not show the correct amount due in case of a group loan without member tracking and the total amount repaid at a given date was greater that the loan disbursed to the first group member (BTracker 3611, Microstart, Burkina Faso).
307. If payment priorities were modifiable, the entry of a loan repayment gave a bug ("Wrong parameters passed to
") and user could have problems paying off a loan (BTracker 3612 and 3613, Microstart, Burkina Faso).
308.User could not enter a loan repayment at menu Group Member Repayments if the group client has 2 savings products, one tracked at group level, the other at member, even though no deposits were entered (BTracker 3645). to top
309. The deletion of a repayment after the write-off date gave an error message (Variable 'lDelLastRepayment" not found, BTracker 3614, Microstart, Burkina Faso).
310. If user deleted a repayment that was a repayment after the written off date, the Loan Ledger Card would generate errors if printed against original dues (BTracker 3636).
311. The Interest Balance on the Outstanding Loans report was supposed to show the recalculated - accrued - interest due as of the reporting date, but it did not (BTracker 3617, World Relief, Kosovo).
312. When a range of loans/clients was selected, the Loan Ledger Card did not show any repayments from the 2nd loan onwards (BTracker 3615).
313. An "Open Table" error occurred when user ran the Payments Made During a Period report (BTracker 3596).
314. Ageing, Arrears and Portfolio at Risk reports have a checkbox where user can indicate whether dues on the reporting date are considered as in arrears or not. If user affirms, the period in arrears increases with 1 day for all loans (BTracker 3649, World Relief, Kosovo). to top
315. The Performance Monitoring report showed the "Open Table" dialog box and could not be run (BTracker 3629).
316. At menu Cheque Clearing, if the "Search" functionality was used to search for a particular cheque number, the information in the text boxes in the upper part of the screen was not refreshed when another cheque number was selected (BTracker 3633).
317. Retrieving a creditor's invoice for which no client had been defined, generated an error ("File 'amyclient' does not exist"). This happened in a multi-branch license if user has not deleted the client's branch codes when saving (BTracker 3634).
318. User could enter debitors or creditors with an idendity number less than 5 characters. This would then cause problems when retrieving this (BTracker 3656).
319. Retrieving a debtor/creditor's payment did not show the correct cash/bank/cheque account (BTracker 3636).
320. If a commission was defined for bounced cheques at configuration and the user changed the status of a cheque to
at menu Cheque Clearing, LPF did not implement the charge on bounced cheques (BTracker 3607). to top
321. An "Open Table" error occurred when user tried to archive old loans (BTracker 3603).
322. When user wanted to print Receipt Parameters at Configuration/Receipts, (s)he would get a error ("Unexpected Parameter passed to function
", (BTracker 3622).
|
