SITE MAP     CONTACT US     DISCLAIMER  
   About Us     Useful Information     FAQs     Financial Education     Complaints   Other Links   Extra Curricular
Search
Period
From  
To  
Archives
   
Home >> Notification - Display
Note : To obtain an aligned printout please download the (10.00 kb ) version to your machine and then use respective software to print the story.
Date: 08/04/2009
RTGS Transactions

RBI/2008/09/426

DPSS (CO) RTGS No. 1776 / 04.04.002 / 2008 - 2009
April 8, 2009
 

Chairman and Managing Director /
Chief Executive Officer of all banks participating in RTGS

 
 

Dear Sir,

 

RTGS Transactions

 

The volume of RTGS transactions is increasing rapidly. RTGS settled 1.94 million transactions in the month of March 2009 as against 0.72 million transactions in March 2008. Customer transactions settling in RTGS presently constitute 89 percent of total RTGS transactions and are growing. At a recent meeting with major banks, we reviewed the entire gamut of RTGS customer transactions with a view to making them more user friendly. Based on these discussions, the following decisions have been taken for implementation by RTGS members.

2. It may be recalled that we had vide our circular DPSS (CO) No. 1607 / 04.04.002 / 2007 - 2008 dated April 7, 2008 advised all RTGS members to comply with the wire transfer guidelines issued by the Reserve Bank of India while originating wire transfers. We had also enclosed prototype of a R41 message format and explained how the message format should capture the details of sender and receiver information. Banks were also required to furnish complete information in field tag No. 5500 and 5561 of customers message format (R-41) as under:-

 
Field tag 5500
 

Line 1

Sender's bank account number /
Country specific unique reference number /
Identification number

35X

Line 2

Name of the Sender/ remitter

35X

Line 3 and 4

Address and Place of Residence

2*35X

 
Field tag 5561
 

Line 1

Account number

[/34X]

Line 2

Name of the Beneficiary

35X

Line 3, 4 and 5

Address and Place of Residence

3*35X

 

3. We understand that while some of the banks are furnishing the required details in the messages, others have not yet implemented the guidelines. It is therefore once again reiterated that in a Straight Through Processing (STP) environment, standardization is very much necessary and uniformity in message format is a pre requisite for the success of STP.

4. RTGS Customers have been complaining that there is no uniformity on information provided to the customer in the pass books / account statements by different banks. Some banks merely indicate `RTGS credit’ without details while other banks are giving sender's bank account number or UTR number of the transactions etc. This is on account of the Core Banking Solution (CBS) of different banks capturing information from different field tags of the message format. As a result, a customer is receiving multiple RTGS credits on a given date, is at a loss to understand the source of funds leading to reconciliation issues.

5.  It is therefore, advised that

a) A bank customer receiving RTGS credit shall be provided with the name of the remitter in his account statements / pass book.

b) A bank customer sending a RTGS remittance shall be provided with the name of the beneficiary in his account statements / pass book.

For the purpose, it is advised that information in field tag no. 5500 and 5561 should be provided uniformly by all banks as advised above. The CBS of the banks should be fine tuned to capture line 2 of field tag no. 5500 for the receiver’s account statement/ pass book and line 2 of field tag no. 5561 for the sender’s account statement/ pass book. The banks are free to provide any additional information as they deem necessary / useful.

6. All RTGS member banks may initiate steps to comply with these instructions latest by June 01, 2009.

Please acknowledge receipt and forward an action taken report in due course.

 
 

Yours faithfully,

 
 

(G. Padmanabhan)

Chief General Manager

 
  © Reserve Bank of India. All Rights Reserved.

Best viewed in 1024x768 resolution in IE 5 and above.