HomeCirculars › RBI/2009-10/109

ECS: Mandate Account Number Accuracy Mandated

No longer current — withdrawn, no replacement on file yet
Source: Reserve Bank of India · RBI/2009-10/109 · issued 29 Jul 2009 · ~2 min read
Quick answerRBI mandates all ECS stakeholders to ensure input files contain only CBS-compatible account numbers. Old 3-4 digit account numbers cause delays and high returns. User institutions, sponsor banks, and destination banks must update mandates, validate files, and filter old numbers to maintain T+1 settlement cycle.

What changed

RBI issued a circular on July 29, 2009, emphasizing that ECS input files must contain only new CBS account numbers. It requires user institutions to call for fresh mandates if needed, sponsor banks to validate and weed out repeatedly returned transactions, and destination banks to filter old account numbers and furnish updated lists to stakeholders.

What it means for you

Banks must ensure their CBS systems are properly interfaced with ECS to enable straight-through processing. Failure to update account numbers will lead to transaction delays, increased returns, and system inefficiency. This is critical for maintaining the T+1 settlement cycle and leveraging National-ECS for centralized processing.

Historical instruction — do not use for current compliance. This is what was required at the time; it no longer reflects current RBI requirements. If no replacement rule is linked above, that only means none is recorded on our register yet — it does not prove no later applicable rule exists. Confirm on the official RBI source below.

What banks were required to do at the time

Who it affects

All banks participating in ECS / National-ECS, User institutions (e.g., utility companies, insurance firms), Sponsor banks, Destination banks, Customers with old account numbers post-CBS migration

❓ Common questions

Regulatory timeline

Built from our lineage records — each fact carries its provenance; missing history simply is not shown (never guessed).

Why is it important to use only new CBS account numbers in ECS files?

Old 3-4 digit account numbers cause processing delays and high returns, disrupting the T+1 settlement cycle. Using new CBS-compatible numbers ensures straight-through processing and timely credit/debit to beneficiary accounts.

What should destination banks do if they receive ECS files with old account numbers?

Destination banks must filter such records branch-wise and user-wise, inform customers to provide new account numbers to user institutions, and furnish updated account number lists to sponsor banks and user institutions.

Who is responsible for ensuring ECS input data accuracy?

Responsibility is shared among individual beneficiaries, user institutions, sponsor banks, and destination banks. Each stakeholder must validate and update account numbers to maintain system efficiency.

📜 Read the original circular — full text as issued by RBI
RBI/2009-10/109 DPSS (CO) EPPD No. 191/04.01.01/2009-2010 July 29, 2009 The Chairman and Managing Director / Chief Executive Officer of all banks participating in ECS / National-ECS Madam / Dear Sir, Electronic Clearing Service (ECS) – Accuracy of Input Data and Completeness of Account Number Information in ECS Mandates /Files ECS was introduced during the early nineties as an efficient method for effecting bulk and repetitive transactions electronically. While ECS (Credit) handles interest, dividend payments, large-volume receipts like utility bills, insurance premia are facilitated by ECS (Debit). Presently, ECS is operational at 76 locations across the country, including the 15 centres run by RBI. Around 20 million transactions are processed every month reflective of increasing efficiency, as the need for issuing and handling paper instruments for such transactions is obviated.  The benefits arising out of ECS operationalisation to the economy as a whole are significant. 2. ECS (Credit and Debit) operates on a T+1 cycle across all locations ('T' refers to the date on which ECS files are processed by the ECS centre. Credit or debit to beneficiary accounts at destination banks is on the next working day). To complete ECS transactions (including the time required for handling returns, if any) within the T+1 cycle, it is imperative that information contained in ECS files is complete, correct and current. Responsibility to ensure this is cast upon individual beneficiaries whose accounts are credited or debited, user institutions, sponsor banks and destination banks. 3. To leverage on Core-Banking Solutions (CBS) in banks for centralised processing of inward instructions and further efficiency in handling bulk transactions, National-ECS has been implemented at Mumbai. Banks have been advised, vide, our circular DPSS (CO) EPPD No. 2283 / 04.01.04 / 2008-2009 dated June 25, 2009 on the steps to be taken for optimal usage and expansion of N-ECS. To adhere to the T+1 cycle in the decentralised local-ECS or to participate in centralised N-ECS, banks need to handle inward data in a straight-through manner with suitable interfaces to their CBS system. Since banks have changed the customer account-number convention post-migration to CBS, presence of old account numbers with 3 or 4 digits in inward ECS data has been causing delays in processing and high returns. For timely credit / debit to beneficiary accounts it is essential that ECS input files contain only the new account numbers; else, there could be delay in processing or transactions might be returned, thus causing a load on the system and making it inefficient. 4. In view thereof, action points which require immediate attention by the different stakeholders include - (i) As User Institutions (a) ECS input files contain only new / changed account numbers of customers (b) Fresh mandates are called for from customers / beneficiaries, if necessary (c) Updates received from destination banks / sponsor banks are duly reflected in the customer records / ECS input files (d) Transactions that are repeatedly returned are not included in ECS input files (ii) As Sponsor Banks (a) Input files received from user institutions are properly validated and transactions repeatedly returned are weeded out (b) ECS data submitted by them contain only the complete and relevant CBS-compatible account numbers (c) Information on updated account numbers received from destination banks is duly conveyed to user institutions (iii) As Destination Banks (a) Furnish list of records with old account numbers along with corresponding new CBS account numbers to respective sponsor banks and user institutions (b) Filter old account numbers in inward ECS files branch-wise and user-wise. Branches to intimate customers to furnish new account numbers allotted to them after CBS implementation to respective user institutions (c) Collect new mandates from customers in cases where the existing mandate has the old account number / requires updation / replacement or otherwise (d) Prepare proper mandate handling policy including putting in place a mandate management system (iv) As Beneficiaries / Customers (a) Mandates / Details with user institutions contain only new account numbers (b) Fill in fresh mandates and furnish them to user institutions, either proactively or if requested to do so. 5. Banks are requested to complete the above initiatives by December 31, 2009.  ECS centres may take proactive steps to return without processing the ECS files which have had more than half the instructions either rejected or returned, unless they are convinced that sufficient care has been taken to weed out or update the relevant information. With effect from January 1, 2010, necessary validations will be built into the ECS / N-ECS process flow to ensure that instructions with old account numbers are rejected at the ECS centre-level itself. 6. Please do the needful and keep us informed of the action proposed to be initiated. Yours faithfully (G Padmanabhan) Chief General Manager
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2009-10/109 · issued 29 Jul 2009. The plain-English explanation above is BankPulse’s own independent summary.
🧰 Tools — save, print, templates & related

💬 Banker Discussion

Discuss this circular with fellow bankers — reply, upvote what helps, report what doesn’t belong. Be professional; no client data. Views are the commenter’s own, not BankPulse’s.

Loading comments…
BankPulse Compliance Evidence Pack — generated 03 Aug 2026 · status cross-checked against RBI’s official withdrawal register (refreshed weekly).
Official RBI source: https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=5192&Mode=0 — Plain-English summary by BankPulse (bankpulse.ai), reviewed by our expert reviewer, CA Amit Jain. Independent platform, not affiliated with the Reserve Bank of India; is our own plain-English paraphrase, not RBI’s original wording.
Public beta — plain-English informational summaries. Always verify against the official RBI source (circular number cited on every page) before making compliance, credit, treasury, audit, or operational decisions. · Join our WhatsApp channel ↗