Loan Performer is the number 1 Microfinance software for MFI institutions worldwide
English French Russian Spanish
Live Support
 
     Updates of version 7.10, 7.09, 7.08, 7.07, 7.06, 7.05, 7.04, 7.03, 7.02, 7.01,7.00
 
Updates of all versions are available through the above links. Crystal Clear is committed to making Loan Performer the best software for Microfinance institutions around the globe.
     
7.05      to top
  The immediate updates below were the first as of June-2005.
1. Correction: if user entered the start of the financial year, it was possible that at entry of a client, a deposit, a loan disbursement or repayment, the program just hang and user had to reboot the application.
2. Correction: while modifying the account type of an account that had no sub-accounts, the user would get errors like "Command cannot be issued within a transaction" and "Function requires row or table buffering".
3. Modification: the date and voucher number can be modified at modification of a financial transaction.

The updates that follow are as of May-2005
1. Correction: in a networked environment users could not enter data simultaneously without getting file lock messages (Chibueze Community Bank, Nigeria, Socodevi, DR Congo).
2. Correction: in a networked environment users could not simultaneously post manually financial transactions without getting errors (like "File access denied" and "Cannot access selected table").
3. Correction: the importation of group members withdrawals gave an error ("Property CashAccount not found").
4. Correction: if a loan disbursement was deleted or if a complete loan was deleted in an SQL Server database, Loan Performer did not make any booking into the general ledger (SMCP, Eritrea).
5. Correction: if user calculated Loan Loss Provision and had individual and group loans and had selected "Show client names", the loan numbers were duplicated (Pulse, Zambia).     to top
6. Correction: Change to PARMEC chart of accounts at System/Configuration/Accounting, caused an error with an SQL Server database.

The following updates are of April - 2005
1. Correction: In Windows98 the resource file could easily become corrupted, causing LPF to give a message at startup saying "File Lang.dbf not found".
2. Correction: Corrected: If at Configuration/Register Part 1, the user selected a GL Account for bounced cheques, the combobox for closing charges became invisible and vice-versa.
3. Corrected: If a client was deleted and re-entered again with the same account number, the user would get a message like "Something went wrong..." when trying to save the information.
4. Corrected: If a deposit was made as a bank transfer and this was later modified and turned into a withdrawal, Loan Performer did not book the modification correctly and used the cash account instead of the bank account for the posting of the correction (SMCP, Eritrea).    to top
5. Corrected: If a deposit was made as a cash transaction and this was later modified and turned into a withdrawal, the modification did only debit and credit the savings account and did not touch the cash account at all (SMCP, Eritrea).
6. Corrected: If a savings withdrawal was modified to a later date, Loan Performer did not update the balance correctly.
7. Corrected: The interest calculation on savings accounts according to monthly minimum balances calculated interest for the first month of the period double (Gamstar, Senegal).
8. Corrected: The Group Members Savings Balances Report was showing incorrect balances for gender at the summary section of the report.
9. Corrected: If VAT was charged on commissions paid at menu item "Payment of Commission" (before or after loan approval), the amount paid was not updated with the VAT part and the booking to the cash/bank/suspense account cheques did not include the VAT part.    to top
10. Corrected: If a loan was entered with a grace period and no interest was calculated on the grace period, the up-front interest showed an incorrect amount (World Concern, Kenya).
11. Corrected: With loans on declining balance having a grace period and no interest is calculated for the grace period, the last instalment could have a negative interest amount at loan application.
12. Correction: The option of group members having different interest rates in a group loan has been removed in 7.04 because we expected no users to be using this option. However as clients complained, we have returned this option (World Hope Int, DR Congo).    to top
13. Corrected: In version 7.04 user could indicate that a guarantor can not guarantee more than 1 active loan. However when user modified a loan application it was still possible to add guarantors who have active loans.
14. Corrected: With configuration setting "Client may apply for a 2nd loan when the first loan is still outstanding" activated but "Receive" de-actactivated and "Follow-up loan only allowed if no arrears" activated, the user would not be able to disburse a group member loan with configuration "Member gets individual loan". Loan Performer would classify this client as a repeat client who already had an existing loan, even when this was his/her first time loan (Arysh, Kyrgyzstan).
15. Corrected: If on a non-English installation user had activated the feature of non-working days and user entered a loan disbursement and one of the instalments fell on a non-working day, LPF updated the date forever and user had to reboot to stop it.
16. Corrected: The importation of multiple (partial) disbursements for the same loan was not working.
17. Corrected: If a loan was disbursed in 2 instalments, it was showing up twice in the Arrears report (World Concern, Kenya).    to top
18. Corrected: If user select to disburse or repay from the savings account, the default savings account was not the selected savings account (Socodevi, DR Congo).
19. Corrected: If user entered stationery or cheque clearing charges as part of the loan repayment for a loan with VAT, the VAT element did not increase.
20. Corrected: When Repaying Arrears From Savings, LPF could not save if the user had not defined a Currency Difference account even if loans were not tied to a second currency.
21. Corrected: If a loan on declining balance was rescheduled with additional instalments and interest, Loan Performer calculated interest wrongly for the additional instalments. This should have been zero interest as the loan is supposed to be repaid after the last instalment.
22. Corrected: The "Payments made during a period" report showed zero dues if user selected 'Include dues without repayments' and there were no payments in the selected period.
23. Correction: The last 2 formats of the report "Listing of Repayments" which had a column for commission paid with every instalment, generated an error saying "Repaid Commission not found".    to top
24. Corrected: If a loan was disbursed by cheque and the whole loan was deleted, the cheque clearing was not reversed in the general ledger (Forde, Uganda).
25. Corrected: If group loans with member tracking and with commission for every instalment were repaid via the menu item Group Member Repayments, the commission due was not repaid.
26. Corrected: The menu option for Group Member Repayment (only available if loans are tracked at group member level) generated errors for loans on declining balance.
27. Corrected: The Group Members Repayment Report was not showing any data for existing repayments.
28. Corrected: The booking of the deletion of a loan repayment that was entered by cheque did not reverse the clearing of the cheque in the general ledger.
29. Corrected: The Active Portfolio per Credit Officer report generated an error ("Variable 'GROUPBY' is not found") when the Grouping/Order is "Loan Number".    to top
30. Corrected: It was not possible to add or modify an account in the general ledger if user was using an SQL database (SMCP, Eritrea).
31. Corrected: The menu option to accrue interest on loans generated an error ("Variable is not found.") after printing a report on accrued loan interest.
32. Corrected: The module for exportation of financial transactions into Quickbooks incorrectly specified the Amount field in case of a deletion of a financial transaction and Loan Performer exported a negative debit or credit transaction (Foccas, Uganda).
33. Corrected: The Amount field in the export file for Quickbooks was not correct in case of loan deletions or inserted repayments. The positive or negative sign was incorrect (Foccas, Uganda).
34. Corrected: The generation of an export file under Day-Closure only used the file indicated by the user if this was a file of DAT format, not for the other file formats (Foccas, Uganda).    to top
35. Corrected: If user ticked all items at "Recalculate Accrued Interest", Loan Performer said that there was nothing to accrue, while if only 1 or 2 items were ticked, interest was accrued.
36. Corrected: If dividend was calculated on shares, Loan Performer was still booking this to the general ledger, even if the month or year had been closed. The same for the modification of a shares transaction, the calculation of interest on savings accounts, the deletion of a time-deposit, the deletion of payment of commission for a loan application, the deletion of a disbursement and repayments.
37. Corrected: the budget report on a non-English operating system generated a bug.
38. Corrected: user could not enter O(ui) or N(on) in the window for the definition of user access rights if a French windows operating system was used (Socodevi, DR Congo).
39. Modified: It is now possible to log user access to each menu item. At Configuration/Users, the supervisor can activate or deactivate the log per user. A report can be generated on the menu items accessed by one or all users from the menu item "Audit Trail".
40. Modified: a new format for the Clients reports with client's birth date is added (MED, Tajikistan).
41. Modified: VAT is also implemented for client's registration fees.
42. Modified: user can disable the modification of client registration and savings account number at client entry (a checkbox is added at Configuration/Register Part 2 saying: "User can modify client registration and savings account number", Entrepreneurs du Monde, France).
43. Modified: a user - at manager level or higher - can set minimum negative balances per client account and charge interest on negative balances. A second interest percentage is added at Configuration/Savings for accounts with negative balances. If an account gets into negative, Loan Performer will apply this interest rate and will DEDUCT this from the total interest received. If the user does not want clients to receive interest at all, the normal interest can be put at zero. The interest calculation is modified for this and also the account closure with the interest calculation to match the above (Chibueze, Nigeria).    to top
44. Modified: a configuration item is added where the user can define whether a guarantor is allowed to guarantee more than 1 outstanding loan. The loan can not be disbursed if this is not activated and one of the guarantors guarantees another loan (Socodevi, DR Congo).
45. Modified: it is now possible to enter loans on declining balance with interest recalculation where the disbursement is in instalments and user repays before the last amount is disbursed. The repayment modules and also the importation of repayments have been modified to suit this.
46. Modified: an option to "freeze" loans on declining balance has been added at rescheduling. If user enters a repayment and "Recalculate interest" is activated, interest is charged up to the indicated date, no interest should be charged afterwards. A loan can also be "unfrozen" (SMCP, Eritrea).
47. Modified: User can now double click on any instalment due on the second page at loan repayment and the first page will automatically become active with the repayment date of the selected instalment.
48. Modified: The entry of loans on declining balance with interest recalculated at repayment was not possible for group members in earlier versions. Now it is.    to top
49. Modified: The report on Fees now has an option to filter on or group by branch (SMCP, Eritrea).
50. Modified: The Day Closure report can be previewed before printing and additional ordering options are added, making it possible to print all transactions of user and each day on a separate page (Forde, Uganda).
51. Modified: The user now has the possibility to modify automatic transactions before the day-closure.
52. Modified: It was not possible to enter transactions in closed financial years (if accounting was activated). This was by design. However we have changed this policy and made it possible to save transactions in a closed financial year. The user is warned that the savings and loan ledgers will be updated but that the transactions will not be booked in the general ledger, thereby creating an imbalance between savings and loan totals from the sub-ledgers and the general ledger accounts that has to be corrected manually (Foccas, Uganda).
7.04      to top
  1. Correction: If the user ran the patch file and selected a different database than the default database, the patch did not run.
2. Correction: If the user modified the contents of the LPF.INI file and put in rubbish, all kinds of errors occurred.
3. Correction: An empty Foxpro database could not be imported to SQL Server.
4. Correction: The importation of clients, savings and loans was not working with an SQL Server database.
5 .Correction: At System / Archiving, user is not able to archive and de-archive in an SQL server database, however user is able to do so in a Foxpro database (KWFT, Kenya).
6. Correction: The backup facility had a problem if the backup path had spaces.
7. Correction: Saving of a new group member took too much time on a large database (KWFT, Kenya).
8. Correction: Ending membership for a group member in a group where other members have outstanding loans, generated a message saying "Specified group member has a loan" even when the member had no outstanding loans and the database was configured for Grameen type loans ("Member gets Individual Loan", KWFT, Kenya).
9. Correction: Operator/data Type mismatch error encountered when transferring client from one group to another (World Concern, Kenya).    to top
10. Correction: If at Configuration/Register Part 1, the user had set the width of the membership number to more than the default number of 4, Loan Performer would still allow the importation of 4-digit group member numbers.
11. Correction: If shares were transferred from one person to another person who did not have a shares' balance, Loan Performer updated the number of the shares of the receiving person incorrectly.
12. Correction: It was possible to have a negative number of shares after simply selling more than the shares' balance.
13. Correction: Importation of loan guarantors gave an error message "Function argument, value, type or count invalid", Line no 26897 in .
14. Correction: At deposits and withdrawals for a large database, after selecting a client and clicking the Next button, the process of loading the Savings Deposits/Withdrawal screen was very slow (KWFT, Kenya).
15. Correction: User was able to enter a date in the future when posting Savings Deposits/Withdrawals
16. Correction: If a group member is transferred from one group to another taking with him his savings balance and a deposit is entered for this member in the new group, the savings balance did not take into account his previous balance (World Concern, Kenya).    to top
17. Correction: If a group member was transferred from one group to another with his savings balance, the group savings balance was updated, but the member's on the Group Member Information page was not.
18. Correction: If user entered a savings transaction for a group with group member tracking enabled and on the first page entered a date before the opening date of the account, then on the 3rd page, entered the member deposits and clicked on 'Save All', (s)he would get a correct message that the transaction date is before the opening date of the account, but after modifying the date on the first page and pressing 'Save' on the first page, the transaction date for the members was still the incorrect date.
19. Correction: During modification of a savings withdrawal where group savings are tracked at member level, an error occurred if the group had an earlier deposit by cheque that was not cleared - Variable 'Blocked' is not found, line no. 8106.
20. Correction: If user changed a deposit into a withdrawal for a savings product with member tracking, the Savers Statement of the group indicated correctly "Savings Withdrawal" in the Particulars column, but the Group Members Savings Statement still read "Savings Deposit".
21. Correction: If clients were entered without a savings account, the importation of savings transactions via DBF files gave an incorrect error message ("Invalid Product", Swabhimaan, India).    to top
22. Correction: If savings transactions were imported and there were savings withdrawals by cheque - which is not possible by manual entry - the user would run into a bug ("Operator/operand type mismatch").
23. Correction: The interest on savings was not calculated correctly if interest was calculated on monthly minimum balances and the interest period was 1 month only.
24. Correction: The starting day of interest calculation on savings accounts was not consistent. Sometimes it fell on the last day of the previous month or sometimes after the first day of the interest calculation month (Gamstar, Gambia).
25. Correction: "Period Savings Report" was not generated if the client had no transactions in the specified period.
Correction: The "Period Savings Report" did not include a deposit if that deposit was made on the date of registration/membership of the client and the reporting period started on the same day.
26. Correction: if the date of membership is less than the start date of the Period Savings report or falls within, LPF did not include the member in the report. LPF also showed the amounts of non-deposit type of transactions and amounts before the period savings.
27. Correction: Members savings report on the "Members Information" page (at Savings/Deposits or Savings/Withdrawals) did not show the correct number of transactions by each member and showed only Cash as mode of transaction even if this was a cheque or bank transfer. The Group Member Savings report under Savings/Savings Reports also showed the incorrect number of transactions by each member. This was always one less.    to top
28. Correction: Group Members Savers Statement printed from the Savings Deposit/Withdrawal screen(s) did not show the correct transaction type and only displayed Cash even if this was by cheque or a transfer.
29. Correction: If user withdrew a Time-Deposit that was entered with interest calculated monthly and interest to be remitted to the savings account, Loan Performer credited the savings account with the Time-Deposit amount only, not including the interest. However the savings balance was correctly updated with time-deposit plus interest.
30. Correction: The option of group members having different interest rates in a group loan has been removed.
31. Correction: If at Configuration/Loan Application Fees, the user had disabled the payment of commissions, but later enabled this feature, when selecting Payment of Commission from the Loans menu, (s)he would be presented with all loans, including loans disbursed and (partially) paid.
32. Correction: On an SQL Server database when several people were entering loan applications at the same time, some loans could get existing loan numbers (SMCP, Eritrea).
33. Correction: If at Loan Application, commission was being charged for every instalment and there were instalments for interest in the grace period, the commission was charged at Group level but not at member level.
34. Correction: Clicking 'Next' on the Loan Application, first page, took too much time on a large database (Grameen lending, KWFT, Kenya).
35. Correction: If a loan was entered with 0 days grace period and the options Calculate interest for grace period and Interest to be paid also in grace period and Interest Calculation in days were checked, an error was generated ("Variable INTOVER is not found", Pulse, Zambia).    to top
36. Correction: The checkbox saying "Separate installment for interest in grace period" was activated according to the definition for individual loans at Configuration/Default loan settings, and not according to group loans, even while user entered a group loan (KWFT, Kenya).
37. Correction: If at Loan Application, page 2, the user clicked on an instalment, then clicked on the checkbox 'All' to change the amounts, the fields for principal, interest and commission were not refreshed with the values of the installment.
38. Correction: At Loan Application (group loan by group member tracking) after saving the application and user selected to print, the option to print "Loans received by group members" occured twice (although the first time it asked for a preview while actually it prints).
39. Correction: If a loan was disbursed with the configurations of Declining Balance Discounted, separate installments in the grace period, interest calculation not in days and disbursement date after the loan application date with recalculation of due dates and interest (option 4) at disbursement, the interest in the grace period was doubled.
40. Correction: If a loan was disbursed with interest deducted at disbursement and the repayment for the interest was deleted and afterwards the user also deleted the loan disbursement the following error was generated: "Error 1495 "Warning: The key defined by the KeyField property for table is not unique".
41. Correction: LPF updated due dates to the next non-working day at disbursement by cheque, even when user had indicated at Configuration/Loans part 2 that this had to be done at cheque clearing.    to top
42. Correction: If a loan on Declining Balance Discounted was disbursed with separate installment in the grace period, interest calculation in days and disbursement date later than the application date and user choose to recalculate dates and amounts based on the disbursement date, the loan ledger card gave a wrong interest balance.
43. Correction: If a loan was disbursed on a date later than the application date and was then deleted and disbursed again on the same date as the loan application date, the instalments were not refreshed.
44. Correction: The process to display the loan repayment screen after the user clicked the Next button after selecting a loan, was very slow (KWFT, Kenya).
45. Correction: If user entered a loan repayment for a group loan with member tracking and the amount is to be withdrawn from the members savings account but the savings balance is not enough and the group has other savings accounts, the user got an error message that the savings balance is not enough. However the product mentioned may not be the correct product.    to top
46. Correction: The field "Balance" on the Loan Repayment screen became modifiable as soon as the user entered the repayment date. This should not have been modifiable at all (ACME, Haiti).
47. Correction: If repayment priorities are not modifiable (Configurations/Loans Part 1), user was still able to modify the repayment of principal, interest, commission when repaying a group loan with member tracking.
48. Correction: If repayment priorities are modifiable (Configurations/Loans Part 1) and loans are tracked at group member level, Grameen lending, at loan repayment of a group loan, the user got an error message ("Total of members does not match the group repayment"). If user changed the configuration to "Repayment priorities are not modifiable", the problem had gone. 
49. Correction: If at loan repayment for a group loan with member tracking, the user clicked on a member-due instalment and modified the amount paid, (s)he could get an error message saying "The total amount paid by the members is different from the sum of the individual accounts."    to top
50. Correction: If user entered a repayment after the last due date of a loan on declining balance type Grameen lending ("Member gets individual loan") and interest is recalculated, the user gets a message "The total amount paid is more than interest and outstanding balance" when saving the payment.
51. Correction: A date that was entered via the calendar on Group Member Repayments screen did not update the displayed balances if interest should be recalculated.
52. Correction: If at repayment user entered a payment on the next due date and closed the loan, Loan Performer did not waive the interest of the 2nd installment, only of the 3rd and later.
53. Correction: If at repayment, user entered an amount for stationery, when saving LPF generated an error message saying "Variable cLabel not found".
54. Correction: Sometimes at loan repayment for loans with Grameen tracking, the error "Variable is not found" (KWFT, Kenya).    to top
55. Correction: If the user entered a loan repayment before the last loan repayment, an adjustment was made in the general ledger to correct the principal and interest parts. This adjustment was given the transaction number of the inserted repayment. This caused a problem if the user later on deleted the last repayment. Loan Performer would adjust only the most recent repayment, but not the adjustment, causing the loan ledger to give different interest and principal balances than the general ledger.
56. Correction: If loans were tracked at member level because of rounding, differences could occur between the dues at group level and at member level for loans on declining balance if interest was recalculated at entry of repayments. Now the user is asked to update the group dues with the recalculated member dues.
57. Correction: If a loan was closed without interest on a date after the last instalment, the interest in arrears was reflected as a negative amount on interest due.
58. Correction: The menu item Group Member Repayments generated an error "Property ANS is not found" when a loan repayment was made and the option "Member gets an individual loan" (Grameen methodology) was activated at configuration.    to top
59. Correction: The Loan Repayments from Arrears did not show any loans to repay if user had individual loans in arrears with savings balances and the option to track group loans at member level was activated. If the last option was not activated, the Loan Repayments from Arrears did show the loans in arrears.
60. Correction: The option to repay arrears from the savings accounts disregarded uncleared cheques and took savings balances for loan repayment that were not yet cleared.
61. Correction: If Arrears were repaid from the Savings account, Loan Performer not only took the arrears balance but also the future dues from the savings account.
62. Correction: For loans on declining balance the interest was not recalculated - even if at configuration this was set as compulsory - when automatically repaying arrears from savings. This could shows up as negative loan balances.
63. Correction: The deletion of a loan that is tracked at member level gave a warning message "Warning: The key defined by the Keyfield property for table Memdues is not unique."
64. Correction: The deletion of a loan disbursement by savings transfer created an error ("Function requires row or table buffering mode").    to top
65. Correction: With Grameen banking, user could not delete a loan repayment (KWFT, Kenya).
66. Correction: If after calculating provision and booking this to the GL, the user deleted a loan, the deletion was booked with the same transaction number.
67. Correction: If under System/Configuration/Loans part1, user activated the checkbox 'Group members have different interest rates', LPF did not compute additional interest when rescheduling individual loans and additional installments were added.
68. Correction: The rescheduling of a group loan with member tracking enabled gave an error and incorrect amounts if user increased the interest for 1 instalment and allocated this to the members. The error was: "Ilegal to attempt a file lock in a transaction after taking prior records locks" (Buusaa Gonofa, Ethiopia).
69. Correction: At rescheduling of a group loan with member tracking enabled, if the user changed the principal amounts per instalment on the first page, then on the second page, clicked "Recalculate Member Dues", then returned to the main page and saved, the due instalments for the members were doubled.    to top
70. Correction: The rescheduling of a group loan with member tracking enabled, without changing anything and on the members page and user clicked on Update Group Dues and went back to the main page, then saved, LPF generated an error message: "Ilegal to attempt a file lock in a transaction after taking prior records locks".
71. Correction: When trying to reschedule a loan that is tracked at member level and changing the interest for the last instalment on the first page as well as on the members page, when clicking the Save button LPF gave an error ("Illegal to attempt a file lock in a transaction after taking prior record locks", SMCP, Eritrea).
72. Correction: If user would reschedule a loan and wanted to update the due dates with say 2 or more months on a monthly loan using the Update All button, LPF was updating the due dates incorrectly.
73. Correction: If several loans were written off automatically, Loan Performer did not remove the interest from the dues tables (Pulse, Zambia).
74. Correction: If for some reason the expiry date field in the loan table contained a .Null. Value, the write-off window only showed loans with lower loan numbers before this record (Pulse, Zambia).
75. Correction: The importation of loan applications gave an error message - Operator/operand type mismatch.
76. Correction: If a loan is written off, it would still show in the Active Portfolio per Credit Officer report.
77. Correction: It was possible to write off a loan before disbursement (Unophone, Uganda).    to top
78. Correction: The guarantors report generated an error - Operator/Operand type mismatch.
79. Correction: If loans were tracked at member level and a member paid off his loan and was transferred to another group, the group-member reports did not show his old loan anymore. For instance the report on loans disbursed since inception did not include member loans that are now in another group (World Hope Int, DR Congo).
80. Correction: The Membership and Group Formation section of the Performance Monitoring Report was not filtered if user selected certain Client Categories (KWFT, Kenya).
81. Correction: The Savings Mobilization section of the Performance Monitoring Report was not filtered if user selected certain Client Categories (KWFT, Kenya).    to top
82. Correction: The last 2 formats of the report Loans/Portfolio reports/Reports on repayments/Listing of repayments gave an incorrect commission amount. It showed the total commission due on the loan but not the commission paid as part of the amount repaid (ID, Haiti).
83. Correction: The Repayments Past Due report did not show certain payments if the date of the payment was equal to the start or ending date of the report.
84. Correction: If changes were made in the Chart of Accounts through the New GL Account button, the Account combo boxes were not instantly refreshed.
85. Correction: If user deleted a complete loan that was disbursed by cheque and the cheque was cleared, the booking of the cheque clearing was not reversed at loan deletion (Forde, Uganda).
86. Correction: If user entered a transaction manually into the general ledger and then modified a single line of the transaction and updated, nothing happened (Pulse, Zambia).    to top
87. Correction: The creation of financial reports that covered a period before 2003 did not include the financial data of the years before 2003.
88. Correction: The Year Closure created an DBF file with the transactions of that financial year. This file was incorrectly saved with the full path into the LPFTable.DBF file. In many cases this would lead to the user not being able to start Loan Performer the next time.
89. Correction: User would get a "File Is In Use" error when running the Income and Expenditure report after running the End of Year procedure.    to top
90. Correction: The Budget report showed an error in a Russian version ("Wrong call to function . No such month available."
91. Correction: Clicking on the Add button did not save new Exchange rate value (under Support Files).
92. Correction: If user was logged in as Supervisor and clicked on the option "Transfer transactions from Header to Non-Header accounts", then closed and clicked on "Create datastructure as file", under menu Tools/Check database, the user could not access any menu item anymore and an message was given ("Class definition ... not found").
93. Correction: If a savings deposit by cheque was imported and the template indicated that the cheque was cleared and accounting was activated, the clearing of the cheque resulted in an incorrect booking where the Suspense account cheques was debited and the bank credited. This should have been the inverse (Mukono Teachers, Uganda).
94. Correction: If at Configuration/Cash Flow, the user defined 2 items with the same name but linked to different GL accounts, the preview showed both labels. This is incorrect. LPF now shows one label.
95. Correction: The menu item Login/Logout under menu System did not log someone out of the last database.
96. Modified: The modification of a savings transaction on a large database took too much time and has been optimised (KWFT, Kenya).    to top
97. Modified: The grace period is shown when client details are displayed at loan approval when user is asked to confirm the loan to approve (KWFT, Kenya).
98. Modified: A new format is added for the disbursement reports that includes a cheque number (Sisdo, Kenya).
99. Modified: The calculation of provision can now be done according to product (Pulse, Zambia).
100. Modified: The option to archive loans to an external database now has a report with the archived loans.
101. Modified: On the page Configuration/VAT a button is put so that the user can directly access the chart of accounts from this page.    to top