SWIFT Charges Explained: What a SWIFT Transfer Really Costs

SWIFT charges are the layered fees that get deducted when money moves through the SWIFT network, and they are the reason an Indian exporter almost always receives less than the invoice amount.

In practice a single wire carries four distinct costs: the sender's bank fee, one or more correspondent (intermediary) "lifting" charges deducted mid-route, the receiving bank's inward charge in India, and a hidden foreign-exchange markup baked into the conversion rate.

The first three are visible if you know where to look. The fourth, the FX markup, is where most of the money quietly goes.

Together these charges commonly cost 1% to 3.5% of the transfer once the exchange-rate margin is counted, far more than the flat fee your bank advertises.

This guide breaks down each layer, explains the OUR, BEN and SHA charge codes, and walks through a worked example on a $4,000 payment so you can see exactly what lands in your account.

It is written for ITeS and SMB exporters in India receiving payments from overseas clients. It is educational, not financial advice.

SWIFT itself is a messaging network. It does not move money; it moves payment instructions between banks.

Understanding how SWIFT payments work helps here: your client's bank sends an MT103 instruction, and the funds are settled bank to bank along a chain of institutions that hold accounts with each other.

Every institution that touches the payment can take a cut, which is why the "charges" are plural.

There are four layers to know:

Sender's bank fee

A flat outbound charge your overseas client's bank levies to originate the wire. Your client usually pays this, so it rarely reduces what you receive, but it shapes which charge code they pick.

Correspondent or intermediary "lifting" charges

When the sending bank has no direct relationship with the Indian receiving bank, the payment hops through one or more correspondent banks.

Each hop can deduct a lifting fee, typically in the range of $15 to $50 per bank, taken straight out of the principal. Two hops means two deductions, and you are rarely told in advance how many there will be.

Receiving bank charge

Your Indian bank may levy an inward remittance handling fee, plus documentation charges such as a Foreign Inward Remittance Advice. These are usually modest, often a few hundred rupees, but they attract GST.

FX markup (the hidden layer)

The bank converts the incoming foreign currency to rupees at its own rate, not the mid-market rate.

That spread, commonly 1% to 3% above the interbank rate, is the single largest cost on most transfers and never appears as a line item.

The flat fees are visible. The markup is not, which is why the amount received rarely matches the maths you did on the invoice.

The table below sets out the typical charge for each layer on a mid-sized inward payment to India. Ranges are indicative and vary by bank, currency and route.

On top of the FX conversion, Indian banks apply 18% GST on the taxable value of the currency-exchange service, calculated on a prescribed slab under Rule 32 of the CGST Rules.

It is small on a single transfer but adds up over a year of monthly settlements.

The uncomfortable truth is that the two costs you can see most clearly, the sender fee and the receiving charge, are usually the smallest.

The correspondent deductions and the FX markup, the two you can see least, are usually the largest.

When your client sets up a wire, their bank asks how the charges should be split. This is the "details of charges" field, and it takes one of three codes.

Which one your client picks decides who absorbs the correspondent lifting fees, and therefore how much reaches you.

OUR

means the sender covers everything, so the correspondent lifting fees are billed back to their account rather than skimmed from the principal. You still lose the FX markup on conversion, but the flat fees do not touch your money.

SHA

(shared) is the default on most platforms. The sender pays their own bank's outbound fee, and every downstream charge, correspondent and receiving, comes out of the amount in transit. This is why a SHA payment nearly always lands short.

BEN

loads all charges onto you, the beneficiary. Avoid asking clients for BEN unless there is a specific reason.

If receiving the exact invoiced amount matters, ask your clients to send OUR and state it on the invoice. It is a one-line request that can save you the lifting fees on every payment.

Assume a US client sends $4,000 on a SHA basis, the most common setup. Suppose the mid-market rate that day is ₹87.50 per dollar. At the true rate, $4,000 is worth ₹3,50,000.

Here is what typically happens on the way to your account.

Step 1, correspondent lifting fee

The payment routes through one intermediary bank, which deducts $20. Now $3,980 arrives at your Indian bank.

Step 2, FX conversion at the bank's rate

Your bank converts at its TT buying rate, roughly 2% below mid-market, so about ₹85.75 per dollar. $3,980 × ₹85.75 = ₹3,41,285.

Step 3, GST on the conversion

On this slab, the taxable value is around ₹2,240, and 18% GST is roughly ₹403.

Step 4, receiving and documentation charge

Your bank levies about ₹200 plus GST, roughly ₹236 in total.

Net credited to your account: about ₹3,40,646.

Against the ₹3,50,000 the money was truly worth, you have lost around ₹9,354, or about 2.7% of the transfer. The $20 lifting fee is a small part of that. The 2% FX markup is the bulk.

On $4,000 that is one payment; multiply it across a year of monthly client settlements and the markup alone runs into lakhs.

Now suppose the same client had sent the same $4,000 on an OUR basis instead.

The correspondent lifting fee is billed back to the sender's account rather than skimmed in transit, so the full $4,000 reaches your Indian bank for conversion.

At the same TT buying rate of ₹85.75, that is $4,000 × ₹85.75 = ₹3,43,000, less roughly ₹405 GST on the conversion and about ₹236 for the receiving and documentation charge. Net credited: about ₹3,42,359. That is roughly ₹1,713 more than the SHA outcome, which is the $20 lifting fee (converted to rupees) that you no longer absorbed.

The FX markup still applies in both cases, so OUR protects your principal from the flat fees but not from the rate spread.

Three things stack up between what your client sends and what you see credited.

First, the correspondent deductions. On SHA and BEN payments, each intermediary bank lifts its fee from the principal in transit.

Because you cannot control how many hops a payment takes, the total is unpredictable, which is the most common complaint exporters raise.

For example, suppose the same $4,000 routes through two correspondent banks rather than one: the first lifts $20 and the second lifts $18, so only $3,962 reaches your Indian bank before conversion, against $3,980 on a single-hop route.

Neither deduction was quoted to your client up front, and a third hop would stack another charge on top. The more banks in the chain, the deeper the erosion, and you learn the final count only after the money lands.

Second, the FX markup. Your bank buys your dollars below the mid-market rate and keeps the difference. This is entirely legal and entirely invisible on the statement, and it is usually the largest single cost.

Third, local charges and GST. The receiving fee, documentation charge and 18% GST are individually small but real.

If you want to understand the timing side of this as well, our guide to SWIFT transfer time covers why multi-hop routing also slows the money down. Fewer hops generally means both lower cost and faster settlement.

There is a fourth factor worth naming: reconciliation error.

Because the deductions are unpredictable, the figure your client says they sent and the figure you record as received almost never match, which creates ongoing friction in your books and in your export documentation.

For a business filing GST returns and matching receipts to invoices, that mismatch is not just annoying, it is compliance work.

Every shortfall has to be explained against the invoice, and the intermediary deductions are the hardest part to evidence because they arrive undocumented.

For example, your client emails that they sent $4,000 against invoice INV-114, but your bank statement shows a credit of ₹3,40,646.

The two figures cannot be tied together directly: back at the mid-market ₹87.50, $4,000 should read ₹3,50,000, so your finance team has to reverse-engineer the gap into a $20 lifting fee, a roughly 2% rate spread and the GST and receiving charges before the receipt can be matched and the FIRA filed.

The $20 hop is the piece with no paperwork behind it, which is exactly what stalls the reconciliation.

This is a real, recurring cost of the SWIFT model that rarely shows up in a fee table but eats into finance-team time month after month.

You cannot remove SWIFT charges entirely on a traditional wire, but you can shrink them.

Ask clients to send OUR, not SHA

This shifts the correspondent lifting fees to the sender and protects your principal. State it on every invoice.

Reduce the number of hops

Payments that route through fewer correspondent banks lose less. Sharing your correct bank details and SWIFT code up front helps your client's bank pick a cleaner route.

Compare the rate, not just the fee

A provider advertising "no fees" but quoting a 3% spread is dearer than one charging a small visible fee at the mid-market rate. Always work out the effective rate.

Consolidate small payments

Fixed lifting and documentation charges hurt proportionally more on small transfers. Suppose a single $20 lifting fee hits a $500 receipt and, separately, a $5,000 receipt.

That $20 is 4% of the $500 but only 0.4% of the $5,000, the same flat charge costing ten times as much in percentage terms on the smaller sum.

At the mid-market ₹87.50, the $20 is about ₹1,750 lost either way, but on ₹43,750 of principal it stings far more than on ₹4,37,500. Where your contract allows, fewer larger settlements cost less per dollar than many tiny ones.

Consider a modern cross-border rail for inward payments

For recurring export receipts, purpose-built platforms often settle closer to the mid-market rate with the fees shown openly.

SWIFT is the global standard for cross-border bank transfers, and for many situations it is entirely appropriate, particularly one-off payments, unusual currencies or corridors where local rails do not reach. It is reliable and universally accepted.

The trade-off is cost visibility: the multi-hop model and embedded FX markup make the true price hard to see before the money arrives.

For Indian exporters receiving regular payments, newer rails change that maths. If you want a fuller comparison of the network options, see our explainer on ACH vs Fedwire vs SWIFT and the broader roundup of SWIFT payment alternatives.

Xflow, for instance, settles inward payments to India at the live mid-market rate with fees shown openly, typically on a T+1 basis, so the conversion spread that drives most of a traditional SWIFT wire's cost does not apply, though the exact difference depends on your bank and route.

TeachEdison, a software exporter, reported saving 60% on payment costs versus SWIFT and roughly 4x versus PayPal and Payoneer after switching.

Xflow holds final RBI PA-CB authorisation for exports and imports, is ISO 27001 and SOC 2 certified, and generates eFIRA automatically for each receipt, so the compliance paperwork that usually adds friction is handled for you.

If you are new to the underlying network, our primer on what is SWIFT sets the context.

The point is not that SWIFT is bad. It is that for predictable, recurring export receipts, a rail built for that job usually costs less and shows you the price before, not after.