RBI mandates account-number-only credit for electronic payments
Current · Source: Reserve Bank of India · RBI/2010-11/235 · issued 14 Oct 2010 · ~2 min read
Quick answerRBI now allows banks to credit RTGS/NEFT/NECS/ECS inward transactions based solely on beneficiary account number, without matching name. This removes manual name-matching delays, enabling straight-through processing. Banks must ensure remitter inputs correct account numbers and can use name field only for post-credit risk checks.
The rule, in the simplest words
Banks must credit money to the account number only, not check the name, for RTGS/NEFT/NECS/ECS (electronic payment systems).
The person sending money must type the correct account number; the bank sending it must double-check it.
The name field is still required in the message but banks can use it only after crediting, for extra safety checks.
Banks must update their computer systems to process payments automatically based on account number alone.
How it plays out — a real example
Ravi, a payments & clearing officer in Indore, processes a customer's NEFT payment to repay a loan. He now only enters the beneficiary's account number correctly, and the system credits it instantly without checking the name, saving time and avoiding delays.
What changed
Previously, banks were expected to match beneficiary name and account number before crediting. Now, for RTGS, NEFT, NECS, and ECS Credit, credit must be based only on the account number. The name field remains mandatory in the message but is optional for destination banks to use for risk-based post-credit checks.
What it means for you
Banks can now automate credit processing without manual name verification, reducing delays and errors. This supports higher transaction volumes and STP. However, originating banks must strengthen maker-checker controls to ensure account number accuracy, including double-entry for internet and branch customers. Destination banks retain flexibility to use name for risk management.
What you must do
Update inward payment processing systems to credit based solely on beneficiary account number for RTGS/NEFT/NECS/ECS Credit.
Implement maker-checker for branch-originated transactions and require double entry of account numbers for internet banking customers.
Place disclaimers on funds transfer screens clarifying that credit is based on account number, not name.
Review risk-based policies for optional use of name field in post-credit checks.
Who it affects
All member banks participating in RTGS, NEFT, NECS, and ECS, Bank operations and IT teams handling payment processing, Branch staff and internet banking teams managing customer fund transfers
❓ Common questions
Does this mean we no longer need to check beneficiary name at all?
No. The name must still be captured and carried in the message. However, for crediting the account, only the account number is relied upon. Banks may optionally use the name for post-credit risk checks based on their own risk perception.
What controls must originating banks put in place for account number accuracy?
For internet banking, require customers to input the account number twice (first entry masked). For branch requests, mandate double writing of account number in the application form and implement a maker-checker process where one employee inputs and another verifies.
Does this circular apply to all electronic payment products?
Yes, it applies to RTGS, NEFT, NECS, and ECS Credit products. The same principle of relying on account number for credit applies to both branch-originated and online/internet channel transactions.
📜 Read the original circular — full text as issued by RBI
RBI/2010-11/235
DPSS (CO) EPPD No. / 863 / 04.03.01 / 2010-11
October 14, 2010
The Chairman and Managing Director / Chief Executive Officer
of member banks participating in RTGS / NEFT / NECS / ECS
Madam / Dear Sir,
Electronic payment products - Processing inward transactions
based solely on account number information
As you are aware, the Reserve Bank of India has introduced various electronic payment products (RTGS, NEFT, NECS and the ECS variants) to facilitate electronic transfer of funds in a secure and efficient manner. The volume of transactions routed through these products has witnessed substantial growth, indicating the acceptance and ease of use, by bank branches and customers alike.
2. The electronic payment products rely extensively on technology for origination, movement, processing and ultimate settlement of instructions. You would agree that any manual intervention not only delays completion of the instruction but also provides scope for error and fraudulent intent. Implementation of core banking solutions (CBS) in banks, software interfaces connecting the CBS platform to the payment system gateways and internet access to customers have been major enablers towards providing a straight-through-processing (STP) environment and, thus, popularising these products.
3. In the CBS environment customers of a bank can be uniquely identified by their account number across branches. In terms of the extant Procedural Guidelines for RTGS / NEFT / NECS / ECS Credit, however, banks are generally expected to match the name and account number information of the beneficiary before affording credit to the account. In the Indian context, given the many different ways in which beneficiary names can be written, it becomes extremely challenging to perfectly match the name field contained in the electronic transfer instructions with the name on record in the books of the destination bank. This leads to manual intervention hindering STP and causing delay in credit or due return of uncredited instructions.
4. Being essentially credit-push in nature, responsibility for accurate input and successful credit lies with the remitting customers and the originating banks. The role of destination banks is limited to affording credit to beneficiary's account based on details furnished by the remitter / originating bank. In order to handle surging volumes in a limited time window, some banks use name matching software, while a few others employ a risk-based approach based on the nature and value of transfer.
5. Keeping in view the foregoing, in the RTGS / NEFT / NECS / ECS Credit products, it has since been decided as under :
Responsibility to provide correct inputs in the payment instructions, particularly the beneficiary account number information, rests with the remitter / originator. While the beneficiary’s name shall be compulsorily mentioned in the instruction request, and carried as part of the funds transfer message, reliance will be only on the account number for the purpose of affording credit. This is applicable both for transaction requests emanating at branches and those originated through the online / internet delivery channel. The name field in the message formats will, however, be a parameter to be used by the destination bank based on risk perception and / or use for post-credit checking or otherwise.
Originating banks may put in place an appropriate maker-checker system to ensure that the account number information furnished by their customers is correct and free from errors. This may entail advising customers enjoying online / internet banking facilities to input the account number information more than once (with the first time feed being masked as in case of change of password requirements) or such other prescriptions. Customers submitting funds transfer requests at branches may be required to write down the account number information twice in the application form.
For transactions requested at branches, the originating bank shall put in place a maker-checker process with one employee expected to input the transaction and the other checking the input.
Banks should put suitable disclaimers on the funds transfer screens in the online / internet banking platform and funds transfer request forms advising customers that credit will be effected based solely on the beneficiary account number information and the beneficiary name particulars will not be used therefor.
Destination banks may afford credit to the beneficiary’s account based on the account number as furnished by remitter / originating bank in the message / data file. The beneficiary’s name details may be used for verification based on risk perception, value of transfer, nature of transaction, post-credit checking, etc.
Member banks shall take necessary steps to create awareness amongst their customers about the need for providing correct account number information while making payments through RTGS / NEFT / NECS / ECS Credit.
The system of providing mobile / e-mail alerts to customers for debit / credit to their accounts will be another way of ensuring that the debits / credits are genuine and put through / expected by them, and preferably, should be extended to all customers for all funds transfer transactions irrespective of value.
The above notwithstanding, in cases where it is found that credit has been afforded to a wrong account, banks need to establish a robust, transparent and quick grievance redressal mechanism to reverse such credits and set right the mistake and / or return the transaction to the originating bank. This particularly needs to function very efficiently and pro-actively till such time customers are comfortable with the new arrangements.
6. These modifications are equally applicable to ECS Debit transactions to be used by destination banks for debiting their customer accounts based on details furnished by the user institutions / sponsor banks.
7. Banks are hereby advised to put in place appropriate systems and procedures to ensure compliance with the above prescriptions. The guidelines are issued under the powers vested with Reserve Bank of India under Section 10(2) of the Payment & Settlement Systems Act, 2007 and would come into effect from January 1, 2011. The instructions would be reviewed and suitable changes will be effected, if necessary, based on operational experience and general feedback.
8. Please confirm receipt of this circular.
Yours faithfully
(G. Padmanabhan)
Chief General Manager
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2010-11/235 · issued 14 Oct 2010. The plain-English explanation above is BankPulse’s own independent summary.
Implement maker-checker for branch-originated transactions and require double entry of account numbers for internet banking customers.
💻 IT / Systems
Update inward payment processing systems to credit based solely on beneficiary account number for RTGS/NEFT/NECS/ECS Credit.
📜 Compliance
Place disclaimers on funds transfer screens clarifying that credit is based on account number, not name.
Review risk-based policies for optional use of name field in post-credit checks.
Grouped from the action items above — a single circular may involve more than one team.
Worked example & action-note template
Example: if you are an IT/Systems lead at a bank this circular applies to (All member banks participating in RTGS, NEFT, NECS, and ECS, Bank operations and IT teams handling payment processing, Branch staff and internet banking teams managing customer fund transfers), your first concrete step on “RBI mandates account-number-only credit for electronic payments” is: “Update inward payment processing systems to credit based solely on beneficiary account number for RTGS/NEFT/NECS/ECS Credit.” (RBI issued this 14 Oct 2010).
Circular: RBI/2010-11/235 -- RBI mandates account-number-only credit for electronic payments
Issued: 14 Oct 2010
Action required: Update inward payment processing systems to credit based solely on beneficiary account number for RTGS/NEFT/NECS/ECS Credit.
Action required: Implement maker-checker for branch-originated transactions and require double entry of account numbers for internet banking customers.
Action required: Place disclaimers on funds transfer screens clarifying that credit is based on account number, not name.
Action required: Review risk-based policies for optional use of name field in post-credit checks.
Owner: ____________ Target date: ____________
Board/committee approval needed? Y / N
Evidence filed in compliance register on: ____________
Built only from this circular’s own published fields — not legal advice; always confirm against the official RBI source.
💬 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.
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=6043&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.
Help us keep this accurate
Found an inaccuracy or have an improvement? Tell us. Every report is reviewed by our team before any change is made — nothing goes live unverified.
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 ↗
BANKPULSE · FREE DAILY BRIEF
Get RBI updates for your role
Every important RBI update, decoded in plain English — for your career, exams & financial awareness.
We collect only your email, name and role, used solely to send your brief — never sold or shared. Withdraw anytime via the unsubscribe link in any email. Independent platform, not affiliated with the RBI. Information, not legal advice.
REPORT AN ERROR · BETA
Spotted an error? Earn 500 BankPulse Credits
Help us stay accurate. If your correction is verified true and approved by our founder, you earn 500 BankPulse Credits — redeemable when the platform monetises.
Reviewed by a human before any credit is awarded. We never change the site from crowd input without verification.
WANT A NEW FEATURE · BETA
What would make BankPulse more useful for you?
Tell us what to build next — a tool, a data view, a role page, anything. We read every suggestion.
Thank you — your ideas directly shape what we build.