Why Indian banks delay or reject NRI transfers: The 7 common reasons and fixes

Key takeaways

• Indian banks don’t reject money transfers upfront. They sometimes pause them mid-way due to back-end checks.
• A ‘Successful’ status on your app often means your bank sent the transfer instruction; it doesn’t mean the money has arrived in India.
• Every international transfer passes through at least three banks: your sending bank, an intermediary bank, and the recipient bank in India. Any one of them can hold the funds.
• Banks run silent compliance checks at each step and are often legally restricted from telling you the reason for a delay.
• Always use the correct purpose code. A mismatch between your transfer reason and your declared code is one of the most common causes of rejection in 2026.
• Send funds to the right account type. Use NRE accounts only for foreign earnings and NRO accounts only for Indian-sourced income, such as rent or dividends, to prevent bank rejections.
• Keep your recipient’s Indian bank account active. An account with no transactions for 24 months gets classified as inoperative and triggers a compliance freeze.
• If your transfer is delayed by more than 5 days, ask your bank for the MT103 or PACS.008 file to find exactly where it stopped.

Many NRI transfers do not fail at the start. They get stuck midway, often without a clear reason. That’s why many users ask why Indian banks reject or delay NRI transfers, even when all details seem correct. The issue isn’t random. Banks follow strict back-end checks, and even one small mismatch can pause or block your funds. 

This is more common now, as India received $135.4 billion in remittances in FY25, according to IBEF. In this guide, we break down the key reasons behind transfer delays and show you how to manage them. Keep reading on.

Money transfer mystery: Why banks don’t disclose it all

Banks often hide the real cause of a transfer delay. According to DBS Singapore, banks must run deep anti-fraud and anti-money laundering (AML) checks, and in many cases, they cannot tell you the exact reason for the hold. 

These silent checks trigger when the system spots risk or changes in your normal transfer pattern. Even a small error, like a wrong purpose code, can set off these checks, as noted by Decentro. Banks may then pause the funds without giving clear updates to the sender due to regulatory restrictions.

The 3-bank chain: Sender → intermediary → recipient

Your money passes through a chain of three or more banks. According to CAGPT, each step uses a SWIFT message called MT103 to pass your payment details along. This acts like a digital ‘passport’ that moves from your bank to an intermediary bank, then finally to the bank in India. If any bank in this chain spots a risk or faces a tech issue, the whole flow can stop or slow down.

• Sender bank: Starts the transfer and sends payment details.
• Intermediary bank: Acts as a bridge, routes the payment, deducts fees and runs compliance checks.
• Recipient bank: Receives the funds and credits the account in India.

Why a ‘Successful’ status on your app doesn’t mean the money is in India

The ‘Successful’ status on your screen means your bank has sent the transfer instruction. It doesn’t mean the money has reached India. 

Here’s why the gap happens:

• Your bank marks the transfer as complete once it leaves their system.
• The intermediary bank may still run checks or process the payment.
• The recipient bank in India has not yet received or credited the funds.
• Each stage follows its own processing time, which can add 1 to 3 business days.

The 7 back-end reasons your transfer is stuck or rejected

Knowing why Indian banks reject or delay NRI transfers puts you in control. Most people find out only after days of waiting, and by then the impact is real—missed rent, late school fees and stress for the family. The good news is that most issues follow clear patterns, and you can fix them early. 

Here are the 7 back-end reasons your transfer is stuck or rejected:

1. Correspondent bank ‘Vetting’ holds

When you send USD or GBP to India, your money doesn’t go straight to the recipient bank. It first stops at a correspondent bank, often based in New York or London, depending on the currency. This bank acts as a middle link between your sending bank and the bank in India. Before it forwards the funds, it runs its own security and compliance checks. It can hold the transfer without asking for approval if it sees a risk or gap in data.

These checks often trigger when:

• Your name or the recipient’s name matches a flagged record.
• The transfer amount is much higher than your normal pattern.
• The sending route is marked as higher risk.
• The transfer lacks clear proof of funds or purpose.

These holds can last 1 to 5 business days. You may not get a clear alert, and even the recipient bank in India may not see any update until the funds clear the step.

2. Purpose code (POR) mismatch

Purpose codes are short labels that tell banks why you send money to India. According to DBS Bank, banks must report every cross-border transfer with the correct purpose code under RBI and FEMA rules, and even small errors can lead to delay or rejection. Banks treat this as a compliance rule, not a small typo, so they pause the transfer until the code matches the transaction type.

Here are two common codes that people mix up:

Purpose code	Meaning	When to use
P1301	Family support	Sending money to support the family in India
P0802	Consultancy income	Payment for professional services

3. SFMS message mismatches

When your transfer reaches India, the SWIFT system must sync with India’s local system called the Structured Financial Messaging System (SFMS). Both systems need to match each detail exactly. 

According to SWIFT, about 65% of payment messages still use unstructured data. By late 2026, banks must remove unstructured address formats under ISO 20022 rules. If a bank in Singapore sends loose or free-text address data, the SFMS system in India may reject the message before credit.

Common causes include:

• Sender address not in the required format
• Name mismatch between the SWIFT message and the Indian bank record
• Wrong or missing IFSC code
• Blank or misfilled data fields

4. Know-your-customer (KYC)/dormant account triggers

KYC is the process banks use to confirm who owns an account. Under RBI guidelines, an account is classified as inoperative when it shows no customer-initiated transactions for 24 consecutive months. If a large international transfer lands in a dormant account, the bank often freezes it right away and starts a review. This step helps prevent fraud, but it also delays access to funds until the account holder completes re-verification.

In most cases, the bank won’t release the money until the account holder submits updated KYC documents. 

Common triggers include:

• No customer-initiated transactions for 24 months or more
• Outdated ID or missing records in the bank system
• Changes in address or contact details have not been updated
• First-time receipt of a large foreign transfer

5. AML (Anti-money laundering) velocity checks

AML checks run in the background on every transfer. Banks use them to track how fast money moves, how often it moves and where it goes. Under India’s AML rules, banks must flag odd patterns and review them before releasing funds. They must also flag sudden spikes in activity and location-based risk signals under RBI guidelines.

One common red flag is ‘round tripping.’ This happens when money moves into India and then quickly moves back out again. Banks treat this as a possible misuse of the system, even if the intent is not harmful.

Patterns that trigger AML flags:

• Many transfers are sent in a short time to the same account.
• Sudden jump in transfer size with no history.
• Funds sent to India are then quickly moved abroad.
• Transfers that don’t match income or job profile.

If the system flags your transfer, the bank may pause it. They may ask for proof of funds or details on the source of money. Some cases are clear in days, but complex ones can take longer due to manual checks.

6. NRE vs. NRO misclassification

NRE and NRO accounts aren’t the same, and banks reject transfers when you send money to the wrong one. According to Business Standard, citing SBI guidelines, NRE accounts only accept funds from overseas remittances or transfers from other NRE or NRO accounts. 

Banks don’t allow Indian-sourced income into NRE accounts. They enforce this rule because NRE accounts stay tax-free in India, so they must keep the income source strictly foreign. If you break this rule, the bank doesn’t just delay the transfer. It rejects it due to compliance checks.

7. New 2026 TCS/TDS validation

From April 1, 2026, India’s foreign remittance compliance changed under the new Income Tax Act 2025. The familiar Forms 15CA and 15CB have been replaced by new Forms 145 and 146. The core requirements stay the same, but the process is now stricter, more digital and has zero room for error after submission. Banks will not process your transfer until the correct forms are filed and verified.

If your total remittance crosses ₹5 lakh in a tax year and the amount is taxable, you must get a CA-certified Form 146 before sending the funds. Form 145 must also be filed online before the transfer, not after. Each transaction needs its own separate filing, and once submitted, the form cannot be edited.

Key checks banks now run before releasing your transfer:

• CA certificate (Form 146) required for taxable transfers above ₹5 lakh
• Form 145 must be filed before the transfer is sent
• No edits allowed after submission
• Each transfer needs a separate filing; no bulk submissions
• Bank verifies tax compliance before releasing funds

If you fail to file or submit incorrect information, you can face a penalty of up to ₹1 lakh under the Income Tax Act 2025. This makes tax validation one of the most common causes of delay in 2026.

The lesser-known reason: Vostro account liquidity

Most people think delays always come from regulatory checks or wrong details. However, another layer sits behind the scenes. It links to how banks move local cash inside India. This is where Vostro accounts come in. A Vostro account is an account that a foreign bank holds with an Indian bank to settle INR payments. When INR funds run low in that pool, transfers can slow down, even if all details are correct.

Banks must match incoming and outgoing INR in real time. If the pool runs short, they pause or group payments until funds refill. That’s why delays can still happen even when all rules are met. 

How a shortage of INR liquidity at the local bank branch can cause ‘Silent delays’

A silent delay happens when banks have correct data, but not enough INR in the Vostro pool to release funds. The system holds the payment until the balance is restored. You may still see ‘processing,’ but no clear error appears.

This often happens during busy periods, like month-end or salary runs. Banks may also group payments instead of sending each one at once. 

Common signs include:

• Transfer shows no error, but stays pending
• No clear update from either bank
• Funds arrive in batches after a delay
• Status clears once the INR pool refills

This isn’t a user error, but comes from timing gaps between banks. At Instarem, we work with established banking partners to keep INR settlement channels running smoothly, so your transfer doesn’t sit in a queue longer than it needs to.

Technical solutions: How to get your money moving

You don’t have to wait in the dark when your money gets stuck. You can use practical tools to track it and push it forward. 

Here’s what to do:

The MT103 request: How to ask your bank for the ‘Global GPS’ of your wire

Banks don’t move transfers blindly. They check if your purpose, documents and beneficiary details match at each step. If something doesn’t fit, the transfer moves into manual review. That’s when you need to request your payment confirmation document.

Most people still call this the MT103, and your bank will know what you mean. It’s worth knowing that as of November 2025, the SWIFT network migrated from the MT103 format to a new standard called PACS.008, which carries richer data and better compliance screening. 

The name changed, but the function is identical; it shows the full path of your money through the banking chain, with timestamps at each stop. It tells you exactly where the delay started and which bank is holding the funds.

Here is how to request it:

• Contact your sending bank’s international payments team.
• Ask for the MT103 or PACS.008 confirmation document for your transfer
• Share your transaction ID and send date.
• Pay a small fee if needed (often USD 20–50 at some banks).
• Wait a few days, based on the bank process time.

Once you get it, you can share it with the recipient bank in India. It helps them trace and locate the funds faster.

Requesting a UETR (Unique end-to-end transaction reference) for real-time tracking

A UETR is a 36-character tracking code for your transfer. SWIFT, which runs global bank messaging, describes it as a parcel tracking code for money. It updates each time your transfer moves between banks or gets held. You can request the UETR from your sending bank. It helps you track status changes in real time instead of waiting for email updates.

SME focus: Resolving business remittance rejections

Business transfers face stricter checks than personal ones. Banks review each payment against invoices, contracts and tax rules before they release funds. This is a key reason why Indian banks reject or delay NRI transfers for SMEs. 

For example, if your invoice shows one amount but the transfer shows another, the bank flags it for review. These checks protect the system, but they also slow down payments if the records don’t match.

To avoid delays, businesses need consistent data across all documents:

• The invoice amount must match the transfer value.
• Sender and receiver names must align exactly.
• The purpose code must reflect the business activity.
• Supporting documents must be ready when requested.

Managing invoice-payment mismatches and 2026 EDPMS reporting deadlines

EDPMS stands for Export Data Processing and Monitoring System. The RBI uses it to track export payments that enter India. Each time your business receives funds for goods or services, the bank must match that payment with the right invoice in EDPMS within a set time frame. In 2026, the RBI tightened checks on this system. If you delay or miss a report, the bank may flag or freeze current and future transfers.

Here’s what you need to manage closely:

• Report export payments within 15 months from the ship or service date.
• Match each payment with the correct invoice in EDPMS.
• Fix any unmatched or overdue entries quickly.
• Share accurate invoice details with your bank’s forex team.
• Avoid repeat errors to keep a clean compliance record.

Final thoughts

Delays in cross-border transfers often come from hidden verifications, not visible errors. You may see a ‘sent’ status, but banks still run checks across systems, rules and data links. Once you understand these points, you can spot issues early and fix them before they block your funds.

At Instarem, we keep these steps clear and easy to track. We help you transfer money with more clarity, so you spend less time chasing updates. You can learn more about Instarem here and sign up and download the app in minutes.

Now that you know what really happens behind each transfer, the next step is to make every transaction clearer and under your control.

Frequently asked questions

Why did my bank reject a transfer with the correct IFSC and Account Number?

A correct IFSC and account number are not enough on their own. Banks also check the name match and purpose code. Even a small name gap, like initials vs full name, can trigger a rejection.

How long should I wait before escalating a delayed transfer?

Most SWIFT transfers take 1 to 5 business days. This depends on the banks in the chain and any checks along the way. If the transfer goes beyond 5 business days, ask the sender bank for the MT103 document.

What is a ‘Purpose code,’ and why is it mandatory in 2026?

A purpose code tells banks why the money is going into India. RBI and FEMA rules require it for every cross-border transfer. Banks use it to check if the transfer matches the stated reason. A wrong code, like marking a business payment as a gift, often leads to delay or rejection.

Can I receive funds from a foreign business into my personal NRE account?

No. NRE accounts only accept foreign income meant for personal use. Business payments must go to an NRO or business account so banks can apply the right tax rules and checks. If you send business funds to an NRE account, banks will reject the transfer due to compliance rules.