₹50,000 is a conditional information threshold, not a general exemption
Under paragraph 74 of the RBI Commercial Banks KYC Directions, a domestic wire initiated by an account holder carries the prescribed originator and beneficiary information regardless of a ₹50,000 threshold. The ₹50,000 boundary concerns the specified non-account-holder domestic route. Cross-border wires require the prescribed information without that domestic threshold. A below-threshold non-account-holder domestic transfer can use the conditional traceable-reference route; it is not an anonymous transfer permission.
Which directions and which banks?
This guide uses the Reserve Bank of India (Commercial Banks – Know Your Customer) Directions, 2025, updated as on 1 October 2026, particularly paragraphs 3–5, 50 and 74. Their defined commercial-bank population excludes Small Finance Banks, Payment Banks and Local Area Banks. Do not assume that every RBI-regulated institution is governed by this particular instrument; identify its applicable directions. The focus here is the ordering-bank and corporate payment-team control file, not foreign-exchange permission or the taxability of the underlying payment.
| Payment route | Initial classification | Operational evidence |
|---|---|---|
| Cross-border wire | At least one financial institution in the chain is abroad | Complete chain and prescribed information |
| Domestic, originator is ordering-bank account holder | Prescribed information irrespective of amount | Account status and payment message |
| Domestic, originator is not ordering-bank account holder | ₹50,000 and above: prescribed information; below: conditional traceable-reference alternative | Amount, traceability and retrieval evidence |
Paragraph 74(1) specifies originator name, the originator account number where an account is used, the prescribed alternative identifying information, beneficiary name and beneficiary account number where used. Without an account, the unique transaction reference must permit tracing to the originator or beneficiary. For the qualifying below-₹50,000 domestic alternative, information must be available by other means and supplied within three working/business days when requested through the specified channel. The direction separately requires immediate availability to the relevant enforcement, prosecuting/competent authorities and FIU-IND on their requests; do not turn three days into a universal response entitlement.
Classify the chain before screening the amount
The definition of a cross-border wire includes a chain in which at least one participating financial institution is in another country. Domestic transfers are chains entirely within India, even if the message system is abroad. A treasury analyst should therefore record participating financial institutions, rather than deciding solely from an INR amount or the location of the software server. Obtain the bank’s message requirements before approving a high-volume payment file.
Batch treatment is narrower than a blanket exemption. For several cross-border payments from one originator, the individual transfers can receive the specified originator-information relief only when their originator account/reference identifiers and the batch file’s required accurate originator and full beneficiary information meet the rule. A control total proves arithmetic completeness, not traceability. Keep a row-level bridge between each beneficiary, amount, account/reference and bank confirmation.
Reject incomplete information and investigate deliberate splitting
The ordering bank must not execute a wire it cannot process in compliance with paragraph 74. A non-account-holder’s intentional structuring below ₹50,000 to avoid reporting or monitoring calls for customer identification. Suspicion is assessed on facts under the PML framework; several legitimate small payments are not automatically proof of an offence, and a threshold worksheet must not be treated as a substitute for judgement. Preserve the reason for the payments and resolve inconsistent beneficiary details before resubmission.
Intermediary and beneficiary banks have their own detection and risk-based follow-up duties. A technical inability to carry information into the related domestic leg does not justify losing it: paragraph 74 specifies at least five years of intermediary records in that situation. Complete wire information is also subject to paragraph 50 record management. Card/PPI purchases of goods or services have a specified exclusion when the required identifier accompanies the transfers, but person-to-person wires through those systems remain covered. The exclusion does not cancel other PML reporting obligations.
Worked illustrations
These illustrations use fictional facts and expressly stated assumptions. Amounts are Indian rupees unless a different currency or unit is specified. They are independent examples, not findings about any actual client.
Illustrative example 1: A small account-holder transfer
A customer orders a ₹12,500 domestic wire from its account at the ordering bank. Although ₹12,500 is ₹37,500 below ₹50,000, the account-holder route still requires the prescribed information. Amount-based software that suppresses the fields below ₹50,000 would misclassify this transaction.
Illustrative example 2: The non-account-holder boundary
Assume a genuine non-account-holder domestic wire, with no suspicious structuring. At ₹49,999 it is ₹1 below ₹50,000 and may use the conditional traceable-reference alternative if all its requirements are met. At exactly ₹50,000 the at-or-above branch applies. Neither branch removes ordinary customer-identification obligations that arise independently.
Illustrative example 3: Deliberate splitting
A non-account holder requests three domestic transfers of ₹19,000 each and expressly says the split is to avoid monitoring. The total is ₹57,000, but the decisive fact for the paragraph 74 structuring instruction is the stated avoidance purpose, not merely that the aggregate exceeds ₹50,000. Customer identification is required. Do not represent three smaller reference numbers as a compliance solution.
Illustrative example 4: A low-value cross-border instruction
A corporate customer orders a USD 75 cross-border wire. The ₹50,000 domestic threshold is not the test and no INR conversion is needed to decide this information requirement. The wire needs the prescribed cross-border information. Separate FEMA, sanctions and bank-policy checks may still determine whether it can proceed.
Illustrative example 5: A batch control total is only one check
One originator submits four cross-border payments of USD 125, USD 200, USD 350 and USD 75. The batch total is USD 750. To use the specified originator-information batch treatment, retain the required originator data in the batch and full beneficiary information for all four traceable payments, with the required individual identifiers. A USD 750 total without the four beneficiary links does not satisfy the information conditions.
Illustrative example 6: The limited three-business-day retrieval clock
Assume a qualifying below-threshold domestic reference-route request is received on Monday, 2 November 2026. Assume Tuesday through Thursday are all working/business days in the applicable calendar, and count the next working day as day one. The three-day sequence is 3, 4 and 5 November, ending Thursday, 5 November 2026. An immediate-enforcement request must not be parked until that date.
Illustrative example 7: Retain information despite a technical break
On 30 October 2026 an intermediary encounters the specified technical limitation in carrying cross-border wire information into the related domestic leg. A five-year anniversary calculation reaches 30 October 2031. Record that as the minimum five-year checkpoint for the retained information, subject to paragraph 50 and any longer applicable requirement or hold; it is not automatic permission to erase the file then.
Ten-step verification table
| Step | Verification | Evidence to retain |
|---|---|---|
| 1 | Identify the bank’s applicable directions | Institution category and current instrument |
| 2 | Classify the complete transfer chain | Participating institutions and countries |
| 3 | Record ordering-bank account status | Customer/account evidence |
| 4 | Apply the correct amount branch | Domestic non-account-holder threshold working |
| 5 | Populate required originator information | Validated name, identifiers and account/reference data |
| 6 | Validate beneficiary and traceability data | Beneficiary details and row-level reference bridge |
| 7 | Check batch-treatment conditions | Single-originator batch file and individual links |
| 8 | Resolve missing information and unusual splitting | Exception, identification and escalation record |
| 9 | Test retrieval and message hand-offs | Working-day calendar, immediate-request routing and intermediary checks |
| 10 | Preserve complete information | Paragraph 50 retention schedule and technical-exception archive |
Sixteen practitioner FAQs
1. Does every wire below ₹50,000 escape the information rule?
No. Determine cross-border status and account-holder status before considering the non-account-holder domestic threshold.
2. What happens at exactly ₹50,000?
Treat it as at or above the boundary for the relevant domestic non-account-holder branch.
3. Is an INR payment necessarily domestic?
Currency is not enough. Establish the participating institutions and the complete chain.
4. Does a foreign message server itself make the transfer cross-border?
The domestic definition expressly accommodates a message system abroad where the financial-institution chain is entirely in India.
5. Can a reference number replace information in every payment?
No. Establish the particular rule permitting its use and ensure it actually supports tracing and retrieval.
6. Is a below-threshold wire necessarily anonymous?
No. The conditional alternative concerns how information accompanies the message, not a right to conceal the customer.
7. Can a corporate batch omit beneficiary-level records?
No. Reconcile every payment to its beneficiary and required identifier; the batch total alone is insufficient.
8. Can payments from different originators be assumed to share the same batch relief?
The specified relief addresses multiple cross-border payments from a single originator. Do not apply it to a mixed file without a separate rule-based assessment.
9. Does repeated small-value activity prove intentional structuring?
Assess the facts and purpose. The worked example states avoidance expressly; legitimate repeated payments require their own evidence and risk assessment.
10. May the ordering bank execute first and repair missing information later?
The ordering-bank instruction prohibits execution when it cannot comply. Resolve the exception before treating the payment as ready.
11. Does a beneficiary bank inherit no responsibility because another bank ordered the wire?
It has its own risk-based missing-information detection and follow-up duties. Record which institution owns each unresolved issue.
12. Do technical message limits excuse destruction of originator details?
No. Preserve the received information under the specific intermediary requirement and the wider record-management framework.
13. Are three business days available for every official request?
No. Distinguish the specified retrieval route from the immediate-availability instruction for the relevant authorities.
14. Are card payments outside all AML requirements?
No. The limited purchase-payment exclusion is not a general exemption from applicable PML obligations.
15. Are person-to-person PPI transfers covered?
The direction distinguishes them from the purchase exclusion; the wire-transfer instructions apply to those person-to-person transfers.
16. Does satisfying this information rule establish FEMA permissibility?
No. A complete message supports the transfer process, while exchange-control permission, sanctions, tax and purpose-document requirements remain separate checks.
Conclusion
Make transfer classification, message completeness and traceability separate controls. Record the reason for any permitted alternative and maintain a clear escalation path for information failures and official requests.