Our References..
  Main PageContact Us
 
 


Reconcilation Reports and Message Error Codes

Reason

Meaning

LNK

LOF

NAK

200

Invalid format

-

-

Y

201

Invalid date

-

-

Y

202

Invalid destination

-

-

Y

203

Invalid message type

-

-

Y

204

Invalid amount

-

-

Y

205

Invalid BLA request

-

-

Y

206

Invalid Priority

-

-

Y

207

Invalid format inquiry number

-

-

Y

208

Invalid (re-used) transaction reference

-

-

Y

210

End of Day in progress

-

-

Y

211

Invalid security Id (ESTS)

-

-

Y

212

Invalid source sub-account (ESTS)

-

-

Y

213

Invalid destination sub-account (ESTS)

-

-

Y

Table 1: Business Message Error Codes


Reconciliation Between the RC and ESTS


An ESTS reconciliation report may be requested during the day from the ESTS centre. In addition, an unsolicited report should be received at the end of day. The message structures are the same, but the internal message types are different: ISR for the requested report, IER for the end of day report.

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).

Receiving The Reconciliation Report


The user can initiate the reconciliation process by sending a ESTS Reconciliation Report Request to the ESTS centre.

The ESTS Reconciliation Report Response arrives at the RC in a series of messages from the ESTS centre. The last message has a flag indicating that it is the last message.

The RC maintains a reconciliation report sub-account database in parallel with the normal sub-account database. On receipt of a reconciliation report component message (either ISR or IER), the reconciliation sub-account database is updated by the details in the message. Once the reconciliation sub-account database has been updated the report component is routed as dictated by the inbound routing table.

On receipt of the last message in an ESTS reconciliation report, the RC generates an alarm telling the user that the last part of the reconciliation report has been received.

Reconciliation Report for Transaction XXXX-BBBBB IIIIIII Received Where:-· XXXX-BBBBB is the bank/branch code initiating the report request, or the bank / branch code supplied by ESTS Centre on IER is the inquiry number of the report request.

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.

Producing The Reconciliation Report (ESTSREC)

This is an off-line program started using the FWCOM ESTSREC command. The most accurate on-line reconciliation is achieved if the user waits for the ESTS reconciliation report to fully arrive before initiating the ESTSREC process.

Inputs

The program is run by the following command:
FWCOM ESTSREC [BBBB]
Where BBBB is an optional bank code for use in a shared RC. If omitted, the report is produced for all banks on the shared RC.

Processing


The program;

a) First checks whether the operator is permitted to produce the report, as for the EFT Reconciliation Report.

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.

Outputs

The report is written to a file

If the RC details match the reconciliation sub-account database details, then only the RC sub-account details are output to the report. If there is a mismatch, then both sets of details are output. If there is no data from ESTS, the appropriate column shows a warning message.

Previous Page..Next  Page..

 

 
Terms of Use | Privacy Statement | Site Map ©2005 Global Bilisim Ltd. All rights reserved