1. Breakout Session Solutions to the Pending Concerns Raised After the 2 nd RB2000 Users’ Conference

2. PROBLEM(S) / CONCERN(S)`SSD Interest Computation Manual computation do not tally with RB2000 System. CAUSEProgramming error SOLUTIONProgramming error corrected Fixes to RB2000

3. PROBLEM(S) / CONCERN(S)Start of Day Takes a Long Time to Process CAUSELarge database log file Non – compliant to the recommended hardware configuration SOLUTIONConduct Regular file maintenance by shrinking of database Install recommended Hardware configuration Upgrade File Server (Note: Using Regular Desktop as Server is not recommended for branches with more than 10,000 accounts especially in LMM) Fixes to RB2000

4. PROBLEM(S) / CONCERN(S)Financial Product Design (FPD) RB2000 does not provide accurate “Next processing date” during dates falling on holidays and/or non- banking days CAUSESystem Error or program bug found Processing date was not properly defined at the FPD SOLUTIONProgram error corrected Check FPD-processing date especially during month-end Fixes to RB2000

5. PROBLEM(S) / CONCERN(S)Loan Management Module (LMM) Negative value appeared with posting Loan Payments and/or Adjustments CAUSESystem Error and program bug SOLUTIONProgram error corrected Fixes to RB2000

6. PROBLEM(S) / CONCERN(S)Loan Management Module (LMM) Wrong Posting of Dues CAUSESystem Error and program bug SOLUTIONProgram error corrected Improvement and Fixes to RB2000

7. PROBLEM(S) / CONCERN(S)Loan Management Module (LMM) Waiving of Penalty charges not functioning CAUSESystem Error and program bug SOLUTIONProgram error corrected Fixes to RB2000

8. PROBLEM(S) / CONCERN(S)Report Generation Inconsistent reports generated CAUSEErrors were caused by inputting of data and non-compliance of procedures Some errors were due to program bug. SOLUTION Re-training of RB2000 users Data inputted should be checked Fixes to RB2000

9. PROBLEM(S) / CONCERN(S)Loan Batch Payment (LBP) Pre-terminated Loan Account or Accounts paid in full prior to maturity were not automatically classified as “Close” CAUSEAutomatic closing of accounts was not included in the Advance Payment specification SOLUTIONShort-term Solution: Manual closing of accounts Long-term Solution: enhance classification of loan status Fixes to RB2000

10. PROBLEM(S) / CONCERN(S)General Ledger Module (GLM) Deleting of subsidiary through Ticket Entry does not function as expected. CAUSESystem error and program bug SOLUTIONProgram error corrected. Fixes to RB2000

11. PROBLEM(S) / CONCERN(S)General Ledger Module (GLM) Incorrect Data passed on to the General Ledger accounts CAUSEContra Accounts were not properly defined at the General Ledger Interface (GLI) module. GLM’s Report Template was not properly defined or not defined at all. SOLUTIONCorrect and complete the report template Correct GLI corresponding debit/credit accounts. Fixes to RB2000

12. PROBLEM(S) / CONCERN(S)General Ledger Module (GLM) GL Summarization not working CAUSEProcedural Error SOLUTION Define “Transaction Group” in FPD Fixes to RB2000

13. Fixes to RB2000 Other common problems encountered: 1.Network cabling not properly installed 2.Shortcut or RB2000 exe lost 3.Wrong posted amount either cash deposit/ withdrawal 4.Wrong transaction code 5.Transaction posted to another account 6.Incorrect check number inputted 7.Communication problems (e.g. no phone, fax, email account etc. 8.Unmanaged back-up files 9.Different database and executable file between client & ASECSoft version. 10. SQL server error

14. FIXES TO RB2000 HOME Thank You!!!