Direct account credit carries specific safeguards
Paragraph 4(c) of RBI's Master Direction on exchange-house Rupee and foreign-currency vostro accounts permits specified direct credits from the RDA Partner Bank to a beneficiary's account at another Recipient Bank. The route includes electronic modes such as NEFT and IMPS and BBPS under the stated conditions. The Recipient Bank credits KYC-compliant accounts; for non-compliant accounts it must perform KYC/CDD before credit or withdrawal. An incoming payment message does not itself establish that this condition is met. RBI Master Direction on exchange-house vostro accounts, paragraphs 4(b)–(c), October 2026.
Keep the two banks' responsibilities visible
The Partner Bank is the AD Category-I bank receiving the inward remittance through its RDA with the non-resident exchange house. It must mark direct-to-account remittances as foreign inward remittances. Accurate originator information and necessary beneficiary information must remain available throughout the exchange-house, Partner-Bank and Recipient-Bank chain. The Partner Bank must add the appropriate foreign-inward and KYC alert specified by the direction. RBI Master Direction on exchange-house vostro accounts, paragraphs 4(b)–(c), October 2026.
KYC completion is not a value threshold
Do not invent a small-remittance exception from the amount of a payment. Apply the actual KYC/CDD requirements. The Recipient Bank keeps the identification and other documents under the applicable PML maintenance-of-records framework; the other RBI KYC/AML/CFT requirements continue. This article does not prescribe an unverified retention period or a new KYC document list. RBI Master Direction on exchange-house vostro accounts, paragraphs 4(b)–(c), October 2026.
Incomplete information needs investigation
The Recipient Bank may seek additional information from the Partner Bank and must report suspicious transactions to FIU-IND with details of the Partner Bank through which the inward remittance arrived. A missing field is not automatically a finding of suspicious activity, and a complete arithmetic total is not an AML clearance. Document the information gap, response and independently assessed action. RBI Master Direction on exchange-house vostro accounts, paragraphs 4(b)–(c), October 2026.
Reconcile the payment chain without merging distinct statuses
Maintain references connecting the exchange-house instruction, Partner-Bank message, Recipient-Bank KYC position and actual beneficiary credit. Operational status buckets such as pending-information, pending-KYC and completed are internal controls, not statutory forms created by this article. Keep the populations disjoint or identify overlaps so a blocked remittance is not counted twice in the reconciliation. RBI Master Direction on exchange-house vostro accounts, paragraphs 4(b)–(c), October 2026.
Scope boundaries matter
The route remains subject to the arrangement's permitted-transaction and other requirements; the message controls do not authorise any otherwise impermissible remittance. The direction also prohibits cash disbursement of remittances under Rupee or foreign-currency drawing arrangements. The illustrations are account-credit reconciliations, not permissions to pay cash, release funds before KYC or bypass suspicious-transaction assessment. RBI Master Direction on exchange-house vostro accounts, paragraphs 4(b)–(c), October 2026.
Applicable primary references
RBI Master Direction on exchange-house vostro accounts, paragraphs 4(b)–(c), October 2026
Six worked illustrations
All facts and amounts below are fictional. Assumptions describe the model, not additional statutory rules.
Illustrative example 1: Reconcile a status population
Ten remittances total ₹5 lakh. Seven completed remittances total ₹3.5 lakh and three pending remittances ₹1.5 lakh. Counts reconcile to 10 and values to ₹5 lakh. The pending amounts do not become eligible for release merely because the totals reconcile.
Illustrative example 2: Do not double count overlapping exceptions
Among 20 instructions, 4 have missing originator information and 3 require KYC follow-up; 2 appear in both groups. Unique flagged instructions are 4 + 3 − 2 = 5, leaving 15 outside those two flag groups. That does not establish that the other 15 pass every applicable control.
Illustrative example 3: Credit only after the stated checks
A model queue contains ₹20,000 and ₹30,000 for accounts with verified completed KYC, and ₹40,000 requiring KYC/CDD completion. The first two total ₹50,000; the third remains a separate ₹40,000 unresolved item. No small-value waiver is assumed for any amount.
Illustrative example 4: Find a beneficiary-credit gap
Five supported instructions are ₹10,000, ₹15,000, ₹20,000, ₹25,000 and ₹30,000, totalling ₹1 lakh. Completed beneficiary credits total ₹80,000. The ₹20,000 difference requires reference-level investigation, including whether a message, KYC or settlement issue remains; it is not automatically a loss.
Illustrative example 5: Reconcile corrected messages
A 12-instruction batch initially has 5 information exceptions. Verified responses resolve 3 and leave 2. Resolved exceptions are 60% of the original 5. That internal completion percentage does not establish that the remaining two can be credited without the required information and checks.
Illustrative example 6: Keep reversed and completed populations distinct
Instructions total ₹2 lakh. Evidence shows ₹1.4 lakh completed credits, ₹0.4 lakh returned transactions and ₹0.2 lakh still pending, with no overlap. The categories reconcile to ₹2 lakh. A return is not a completed beneficiary credit, and a pending instruction is not erased from the review because the settlement total balances.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Establish the permitted RDA route | Approved arrangement and underlying transaction scope. |
| 2 | Identify both banks | Partner Bank and Recipient Bank references. |
| 3 | Check foreign-inward marking | Actual electronic message indicator. |
| 4 | Verify originator and beneficiary data | Information retained throughout the payment chain. |
| 5 | Check the required alert | Foreign-inward and KYC warning information. |
| 6 | Confirm recipient KYC/CDD position | Completion evidence before the permitted credit or withdrawal. |
| 7 | Resolve additional-information requests | Partner-Bank responses and reference-level conclusions. |
| 8 | Assess suspicious activity separately | Applicable reporting decision and supporting evidence. |
| 9 | Reconcile final statuses | Credits, returns and pending items without double counting. |
| 10 | Retain the review trail | Recipient records and applicable KYC/AML/CFT compliance evidence. |
Sixteen practitioner FAQs
1. Who is the Partner Bank?
The AD Category-I bank receiving the inward remittance through its RDA with the exchange house.
2. Who is the Recipient Bank?
The other bank holding the beneficiary account in the paragraph 4(c) route.
3. Does the route include electronic transfers?
Yes. The direction identifies electronic modes such as NEFT and IMPS and BBPS subject to its conditions.
4. What should identify a direct-to-account payment?
The Partner Bank must appropriately mark it as a foreign inward remittance.
5. Whose information must travel in the chain?
Accurate originator information and necessary beneficiary information.
6. Does the information stop at the Partner Bank?
No. It should remain available throughout the specified payment chain.
7. What alert should the Partner Bank add?
The prescribed foreign-inward alert indicating that credit must not go to a KYC-non-compliant account.
8. What if the recipient account is not KYC compliant?
The Recipient Bank must complete KYC/CDD before the relevant credit or withdrawal as required by the direction.
9. Is there an amount-based KYC waiver in this paragraph?
Do not invent one from the remittance amount.
10. May the Recipient Bank request more information?
Yes, it may seek additional information from the Partner Bank.
11. Does every missing field automatically prove a suspicious transaction?
No. Assess facts and applicable AML obligations separately.
12. Where are suspicious transactions reported?
The direction requires reporting to FIU-IND with the Partner-Bank details specified there.
13. Who maintains recipient identification records?
The Recipient Bank under the applicable record-maintenance framework.
14. Does this guide set a new retention period?
No. Apply the independently applicable requirements.
15. Can a returned remittance be counted as a completed beneficiary credit?
No. Preserve distinct statuses and supporting references.
16. Does a balanced reconciliation permit cash disbursement?
No. The direction's prohibition on cash disbursement and other conditions continue.
Conclusion
Review direct-to-account RDA remittances by separating partner-bank message duties, recipient-bank KYC controls and the evidence connecting each beneficiary credit.