How the reconciliation report is requested during the day, and how reconciliation data is stored and printed (either for the requested report or the unsolicited report at the end of the day).

It is important to note that the on-line reconciliation process compares snapshots of the reconciliation data taken at different times. As this is during the business day, transactions may be affecting the data in the time between these snapshots, thus discrepancies do not necessarily indicate accounting problems.

This is an off-line program started after EOD processes.

The most accurate on-line reconciliation is achieved if the user waits for the ESTS reconciliation report to fully arrive before initiating the RECON process.

The program is run by the following command:
GB RECON

a) Where is an optional bank code for use in a shared RC. If omitted, the report is produced for all banks on the shared RC.

b) If no bank code was specified,
• Displays the date and time at which the report was last run to the user;
• Requests confirmation from the user that the report should be run before continuing;

c) Reads and sorts the reconciliation sub-account database into security identifier within Sub-account type order;

d) Reads the sub-account records from the RC database, and again sorts into security identifier within Sub-account type order;

e) Compares the sorted data and produces a report as detailed below.

The report is written to a file GB_RECON_xxxx_yymmdd.TXT, where xxxx is the participant's bank code and yymmdd is the current business date.