SWIFT vs Local Transfer: Speed, Cost and Which to Use

If you export services from India and get paid by clients in the US, UK or Europe, the route their money takes decides how much you keep and how long you wait.

A SWIFT transfer is an international wire: SWIFT carries the payment instructions, and the money moves through a chain of correspondent banks. A local transfer uses a country's own domestic payment rails, such as ACH in the US, SEPA in Europe or Faster Payments in the UK, so it is usually cheaper and settles the same or next business day. SWIFT reaches almost any bank in the world; local rails work only inside supported countries.

For regular payments from major markets into India, receiving through local rails is normally cheaper and more predictable, while SWIFT stays useful where no local route exists. See how swift payment works for the messaging behind it.

No, SWIFT does not move money itself. It is a secure messaging network that banks use to send each other payment instructions, identified by each bank's SWIFT code (BIC). The money moves separately, through accounts that correspondent banks hold for one another.

That chain is SWIFT's strength and its cost. Almost every bank connects to it, so a wire can reach practically anywhere, but each bank in the chain can take a fee and add time. About 75% of SWIFT cross-border payments pass through at least one correspondent bank, with 1.3 intermediaries on average, according to Papaya Global's analysis; see correspondent banks.

SWIFT has also changed. Its gpi service gives each payment a tracking reference (UETR), so banks can see where it is and what was deducted, and the industry is moving from the older MT103 message to the ISO 20022 standard, which carries richer payment data; see swift mt103.

A local transfer moves money on a country's domestic rails, the same systems residents use to pay each other: ACH and Fedwire in the US, SEPA in Europe, Faster Payments in the UK and NEFT, IMPS and RTGS in India.

India's rails cannot accept a payment from another country, so a foreign client cannot send dollars over NEFT. To receive locally, you use a provider that holds receiving account details in the client's country:
1. Your US client pays by ACH into a US account held for you, as if paying a local supplier.
2. The provider converts the dollars to rupees.
3. The rupees reach your Indian bank account over Indian rails, with a FIRA as proof of the export payment.

Because the payment never crosses a correspondent chain, nothing is deducted on the way. Two things change, though: the provider often appears as the sender on your statement, so ask clients to put your invoice number in the payment reference, and the route works only in the countries the provider supports; see receiving accounts.

A local transfer sends money between two accounts in the same country, in that country's currency, on its domestic rails. An international transfer sends money to an account in another country, usually with a currency conversion, so it uses SWIFT and correspondent banks or a cross-border provider, and it falls under both countries' foreign exchange rules.

So a ₹50,000 NEFT from Mumbai to Pune is a local transfer, while $5,000 from a client in Texas to your Indian account is an international transfer, whichever route carries it.

Most SWIFT transfers now arrive within a day. SWIFT reports that nearly 60% of payments on its gpi service are credited to the beneficiary within 30 minutes and almost all within 24 hours, and Statrys measured an average of about 18 hours across 2,000 of its own outgoing SWIFT payments.

• Older routes and banks not on gpi are slower.
• Exotic currencies need more correspondent hops.
• Cut-off times, weekends and holidays in any country on the route add days.
• Compliance checks at an intermediary bank can hold a payment.

On the Indian side, your bank may also wait for you to confirm the purpose code or provide documents before converting and crediting the money, which is often where an inward wire loses a day or two. A local transfer usually settles the same or next business day; see swift transfer time.

A SWIFT payment costs more because each bank in the chain can take a fee, and because the bank that converts the money uses a rate worse than the market rate. The second cost is usually the larger one and does not appear as a fee on your statement.

• Fees along the chain: a sending fee, one or more correspondent charges taken from the amount in transit, and a receiving fee at your Indian bank. Typical bank charges run about $30 to $45 to send and $15 to $20 to receive, by Papaya Global's figures.
• Exchange markup: when the dollars convert to rupees, banks usually apply a rate 1% to 3.5% below the market rate, often costing more than all the fees together.

OUR, SHA and BEN: who pays the fees

When your client sends a SWIFT wire, they choose a charge code. With OUR, they pay all fees and you receive the full amount. With SHA, they pay their bank's fee and correspondent and receiving fees come out of your money. With BEN, every fee is taken from what you receive. Most business wires default to SHA, which is why exporters are so often paid short, so agree OUR or state the charge code on your invoice.

Worked example: your client sends $7,000 by SHA wire, at an illustrative mid-market rate of ₹95 (fair value ₹6,65,000).

RTGS is India's domestic system for large rupee payments, run by the Reserve Bank of India: it settles each payment of ₹2 lakh or more between Indian banks in real time. SWIFT is a global messaging network that carries payment instructions between banks in different countries; it does not settle money itself.

The two meet on an inward payment: a client abroad sends a SWIFT wire, and once your bank converts it, the rupees may move within India on domestic rails. For how RTGS compares with India's other rails, see rtgs vs neft.

SWIFT is not obsolete, and in some cases it is the right tool.

• Unusual destinations, where a client's country or currency is not covered by local routes.
• One-off large transfers, where the counterparty insists on a bank wire.
• Payments that need a bank's full SWIFT confirmation trail, such as some trade-finance deals.

For a steady flow of payments from major markets, though, its cost and unpredictability are hard to justify when a local route exists; see swift payment alternatives.

Receive locally if your clients are in the US, UK, Europe or another market a provider covers and they pay you regularly; use SWIFT if the client is in a country without local routes, insists on a bank wire, or pays once in a large amount.

• Regular invoices from the US, UK or EU: local receiving account, so the full amount arrives and converts near the market rate.
• Client in a less common country: SWIFT wire, with OUR charges agreed on the invoice.
• Large one-off payment: compare the bank's quoted rate with the mid-market rate before accepting a SWIFT wire.

Before choosing a provider, check the exchange rate against the mid-market rate, the total fee per payment, how quickly rupees reach your bank, and whether every payment comes with a FIRA and the right purpose code.

Xflow, for example, gives clients local account details in their own country and settles INR to your Indian bank account at the live mid-market rate, with an eFIRA for every international transaction.