Speed does not replace the funding control
Section 5(C) of RBI's Master Direction on exchange-house Rupee/foreign-currency Vostro accounts addresses Speed Remittance Procedure. Ordinarily, the exchange house funds the rupee account through the AD Category-I bank's nostro in advance, before payment instructions. The bank verifies data and available vostro balances before issuing beneficiary drafts or credits. This guide uses the direction updated on 1 October 2026 and checked on 28 October 2026; it focuses on release controls rather than a general remittance onboarding checklist. RBI RDA Master Direction: sections 5(C), 7(b), 3 and 8.
Identify the account and authority for the speed arrangement
Section 5(C)(a) addresses extension of speed remittance to an existing drawing arrangement, including a separate rupee account and the stated prior-approval rule. It also provides the exception for satisfactory operations under an existing DDA or Non-DDA arrangement, subject to usual conditions and necessary documents, with immediate RBI information. Document which route the bank has actually used. An approved ordinary RDA should not simply be renamed speed remittance in the payment system without reviewing those conditions. RBI RDA Master Direction: sections 5(C), 7(b), 3 and 8.
An instruction and a funding advice are different evidence
The exchange house sends complete payment details via SWIFT or internet. A funding message is not by itself confirmation that the bank's nostro has received money or that the relevant rupee vostro has been credited. Maintain linked timestamps for funding receipt, account credit, data verification, reservation and beneficiary payment. Section 7(b) specifically requires concurrent audit coverage to ensure vostro credit precedes beneficiary payments. A later end-of-day match cannot alone demonstrate that sequence. RBI RDA Master Direction: sections 5(C), 7(b), 3 and 8.
Measure the payment path the system actually uses
Section 5(C)(b) allows the bank to determine collateral, if any, considering factors including prefunding, track record and whether payments operate gross in real time or net through file transfer. A file's net amount and its gross payment instructions can create different intraday funding needs. Define the actual settlement sequence and available-balance calculation. Do not count an unconfirmed incoming credit as spendable just because it appears in the same file or because the final net position is positive. RBI RDA Master Direction: sections 5(C), 7(b), 3 and 8.
Reserve queued payments to prevent double use of a balance
As an operational control, maintain unique instruction identifiers and a reservation register alongside the ledger balance. Subtract live commitments already earmarked for release when assessing a new instruction, and release a reservation only after verified cancellation or rejection. This reservation model is a recommended implementation control, not an additional RBI formula or threshold. It helps the bank satisfy the direction's credit-basis and monitoring requirements where several channels read the same balance simultaneously. RBI RDA Master Direction: sections 5(C), 7(b), 3 and 8.
Keep collateral policy separate from payment money
Unlike importing a fixed number of collateral days from another RDA procedure, section 5(C)(b) permits the AD bank's own policy based on the listed risk factors. Record the approved measurement basis, review triggers and exception authority. A guarantee or blocked collateral deposit is not automatically the same as cleared, available rupee funds in the payment account. Sections 3 and 8 retain the credit-basis/no-overdraft requirements. Do not treat collateral coverage as permission to ignore them. RBI RDA Master Direction: sections 5(C), 7(b), 3 and 8.
Reconcile the release trail and act on exceptions
At close, reconcile accepted instructions, holds, rejections, duplicates, reservations, posted debits, beneficiary results and available balances. Escalate funding credited after a payment, unsupported manual releases and repeated reservation overrides for investigation. Retain the evidence for concurrent audit. No universal ₹ amount, percentage buffer or processing cutoff is invented here: the numerical illustrations use explicitly fictional bank policies and queues, without changing RBI's underlying conditions or wider KYC/AML obligations. RBI RDA Master Direction: sections 5(C), 7(b), 3 and 8.
Applicable primary references
RBI RDA Master Direction: sections 5(C), 7(b), 3 and 8
Six worked illustrations
All facts and amounts below are fictional. Assumptions describe the model, not additional statutory rules.
Illustrative example 1: Available balance after live reservations
Assume confirmed rupee vostro balance ₹12,00,000 and existing live payment reservations ₹3,00,000. Uncommitted balance is ₹9,00,000. Reserving a further valid ₹8,00,000 instruction leaves ₹1,00,000. The release must still meet the bank's verification and actual posting controls.
Illustrative example 2: Advice is not confirmed money
An exchange house advises an incoming ₹10,00,000 transfer, but confirmed usable vostro balance is zero. A ₹10,00,000 beneficiary batch therefore has a ₹10,00,000 funding gap at that point. Do not change the confirmed balance merely by importing the advice into a spreadsheet.
Illustrative example 3: Net file arithmetic can hide a gross-path gap
Confirmed available balance is ₹12,00,000. A file contains gross beneficiary payments ₹18,00,000 and an expected, unconfirmed incoming credit ₹7,00,000. The apparent net outflow is ₹11,00,000, leaving a theoretical ₹1,00,000. But a process releasing gross debits before that credit needs ₹18,00,000 and has a ₹6,00,000 gap. This is not authority to net an unconfirmed receipt.
Illustrative example 4: Concurrent channels need one reservation view
Two channels each receive a valid ₹6,00,000 instruction and independently read the same ₹10,00,000 available balance. Combined demand is ₹12,00,000, exceeding it by ₹2,00,000. Reserving the first leaves ₹4,00,000, so the second cannot be fully reserved from that balance. Neither channel should count the original ₹10,00,000 again.
Illustrative example 5: A fictional collateral policy is not an RBI percentage
Assume a bank's duly approved speed-remittance policy requires collateral at 20% of its assessed ₹30,00,000 peak exposure. The policy amount is ₹6,00,000; existing eligible collateral ₹4,00,000 leaves ₹2,00,000 to arrange. The 20% is invented for this example, and the collateral does not itself become available beneficiary-payment funds.
Illustrative example 6: Reconcile payments, queues and duplicates
A confirmed starting balance ₹15,00,000 has posted valid beneficiary debits ₹4,00,000 and remaining valid reservations ₹3,00,000. Ledger balance is ₹11,00,000 and uncommitted balance ₹8,00,000. A separately identified duplicate message for ₹2,00,000 is held for investigation and excluded from the valid new-payment population; paying it would create an unsupported second debit.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Identify the arrangement | AD bank and exchange-house account identifiers |
| 2 | Confirm the speed authority | Approval or applicable extension exception evidence |
| 3 | Verify complete payment data | Authenticated messages and unique identifiers |
| 4 | Confirm actual funding | Nostro receipt and corresponding vostro credit |
| 5 | Identify gross or net processing | Documented real settlement sequence |
| 6 | Reserve accepted instructions | Shared commitment ledger and cancellation controls |
| 7 | Apply the bank's collateral policy | Approved factors, coverage and review record |
| 8 | Check each release | Available balance, data verification and timestamp |
| 9 | Reconcile exceptions | Holds, returns, duplicates and manual overrides |
| 10 | Preserve concurrent-audit evidence | Funding-before-payment trail and corrective action |
Sixteen practitioner FAQs
1. Which RBI provision addresses speed remittance?
Section 5(C) of the exchange-house Vostro Master Direction.
2. What is the ordinary funding sequence?
Advance funding through the bank's nostro into the relevant rupee account precedes payment instructions, with verification before beneficiary release.
3. Is a transfer advice proof of usable vostro money?
No. Verify actual receipt and the corresponding account credit.
4. Does SWIFT transmission itself prove sufficient funds?
No. Message authenticity and funding availability are separate controls.
5. Can an existing DDA exchange house use speed without any review?
Check the direction's satisfactory-operation exception, usual conditions, necessary documents and immediate RBI-information requirement.
6. Is there one mandatory seven-day collateral formula for speed remittance?
Section 5(C)(b) permits a bank-determined policy based on the listed factors; do not transplant another procedure's formula.
7. What factors does the direction identify for that policy?
Prefunding, exchange-house track record, gross versus net processing and other relevant factors.
8. Can a guarantee be treated as spendable rupee account money?
Not merely because it covers exposure; establish actual availability and legal terms separately.
9. Does collateral permit an ordinary vostro overdraft?
Do not treat it as an exemption from the direction's credit-basis/no-overdraft requirements.
10. Why distinguish gross debits from a file's net outflow?
Their sequence can produce different funding needs before expected credits arrive.
11. Is the reservation formula itself prescribed by RBI?
No. It is an operational control proposed here to avoid using the same balance twice.
12. When should a cancelled instruction's reservation be released?
After verified cancellation or rejection under the bank's control process, not an unsupported request.
13. What is a useful duplicate-payment control?
A unique instruction identity tied to the acceptance, posting and beneficiary-result trail.
14. Can end-of-day sufficiency prove every earlier release was funded?
No. Preserve timestamps demonstrating the relevant funds existed before each payment.
15. Where does concurrent audit enter the analysis?
Section 7(b) requires coverage of funding credit before beneficiary payment.
16. Does this replace KYC/AML review?
No. The funding controls operate alongside the direction's applicable KYC/AML/CFT and due-diligence requirements.
Conclusion
Control speed-remittance releases using confirmed funding, reserved instructions and the bank’s documented collateral policy under RBI’s RDA directions.