NRO Account Repatriation Limit (USD 1 Million): exact rule flow, Form 15CA/15CB timing, and common failure points

Most repatriation delays are not legal ambiguity. They are sequence mistakes. This guide separates eligibility, tax documentation, and bank execution so your file can clear in one pass.

Updated 09 May 20266 min read
An editorial illustration of compliance documents, bank transfer pathways, and a USD limit marker for NRO repatriation planning.

What the USD 1 million limit actually means (and what it does not mean)

The high-intent search phrase is correct in spirit, but often misunderstood in execution. The USD 1 million figure is generally treated as an annual facility for eligible remittance of assets from NRO balances under the prescribed framework and documentation conditions. It is not a universal one-click transfer promise for every transaction shape.

In practice, banks evaluate source trail, tax compliance, and your current status before they evaluate speed. So the most useful framing is not 'what is the limit?' but 'which lane is this transfer in, and does my file prove that lane cleanly?'

Use this lane check before filing transfer requests

QuestionIf answer is yesWhy it matters
Is the money currently in an NRO account or clearly attributable to an NRO-eligible source?Proceed in NRO remittance lane with tax and source documents.Classification errors are the top cause of rejection loops.
Is this just foreign savings held abroad being sent into India?Do not treat it as NRO repatriation.Inward remittance and NRO remittance are different workflows.
Are you moving funds abroad from India-side balances?Prepare bank and tax compliance pack first, then execution.Documentation sequence matters more than provider marketing claims.
Are you combining multiple sources in one transfer request?Split requests by source when needed.Mixed-origin files trigger deeper scrutiny and delays.
Clear classification before initiation prevents most avoidable compliance friction.

Execution sequence that reduces back-and-forth

Treat this as a file-building workflow, not an app workflow.

Step 1

Create a source-of-funds memo for yourself first

List each component amount, origin, and holding period. If you cannot explain the source cleanly in one page, your bank reviewer will also struggle.

Step 2

Align tax-compliance paperwork before transfer booking

Where applicable, complete Form 15CA flow and CA certification path in the correct order as required by your bank and transaction type.

Step 3

Submit a complete bank pack in one shot

Include KYC, account proofs, purpose notes, source proofs, and tax docs. Partial submissions create avoidable review cycles.

Step 4

Lock beneficiary details and receiving-lane logic

Confirm the destination account ownership and receiving-country requirements before release to avoid returns or amendments.

Document checklist (bank-specific formats will vary)

  • Identity and KYC documents as requested by the remitting bank.
  • NRO account details and statements relevant to source tracing.
  • Source evidence (rent, sale proceeds, inheritance, or other qualifying trail).
  • Tax workflow documents including 15CA details and, where required, 15CB support.
  • Beneficiary account proof and transfer purpose statement.
  • A self-audit note that total amount requested remains within your annual facility context.

One phrase to remember

The limit number gets attention, but sequence gets approvals. Classification -> tax workflow -> bank pack -> transfer release.

Is the USD 1 million facility a guaranteed automatic transfer entitlement?

No. It is a regulatory facility subject to conditions and documentation. Banks still review source, tax workflow, and execution details before release.

Do Form 15CA and 15CB always apply the same way?

No. Applicability depends on transaction nature and tax context. Your remitting bank and tax advisor should confirm the exact path for your case.

Can I combine all balances into one transfer request to save time?

Only if the source trail is clear and the bank accepts the combined file. Mixed-origin requests often move faster when split with separate documentation trails.

Is this article legal or tax advice?

No. This is an execution framework to reduce process errors. Final decisions should be validated with your authorised dealer bank and qualified tax professional.