This activity is primarily aimed at checking up the static table maintenance input against the original source documents and spreadsheets used for the input. This will be the first level check leading to detailed check in the next stage of System Trial run. A broad list of reports that can be used for database call back is included in this section. More specific strategies should be evolved based on the criticality of the data and the database design. Database call back exercise should be preferably undertaken by set of staff not involved in the input, internal control department should also be involved. The called back reports should be authenticated by the concerned authority from the bank and should be kept aside for future implementation or system audit.
The Maintenance changes log report can be used to identify all the maintenance carried out and can be used for the call back. It is suggested that this report be used to fully check all the database setup done at the bank. In addition, reports/dumps of the data in various tables can be printed to check with the source sheets.
Static Maintenance
General Ledger
Currency
Reports
Maintenance Changes Log Report
Customer Maintenance
Customer accounts
Interest & Charges
Brokerage
Tax
Bills
LC
Product Report
End of Cycle
Process Definition Print
In addition to these reports, adhoc reports should be generated for checking any other maintenance.