What Is a SWIFT Code? Structure, Uses and Payroll Costs

Nearly every explanation of a SWIFT code calls it a Bank Identifier Code and labels its four blocks bank code, country code, location code and branch code. Two of those labels are wrong and the name itself is out of date. That matters less than the second problem: the code tells you almost nothing about what the payment will actually cost, and for anyone running international payroll that is the only question that matters.

We move payroll across borders, so we see the consequences rather than the theory: salaries arriving short, arriving late, or failing validation because the wrong identifier went in the wrong field. This guide decodes the code properly against the standard that defines it, separates it from the identifiers it gets confused with, and then covers what a SWIFT payment really costs a payroll run.

What is a SWIFT code?

A SWIFT code is a standardised identifier for a financial institution. Its formal name is the Business Identifier Code, or BIC, and it is defined by the ISO 9362 standard. Its job is to tell the international payment network which institution a message is addressed to. It identifies the institution, and it never identifies an account.

Note the name carefully, because this is the most repeated error on the topic. It is the Business Identifier Code under ISO 9362, not the Bank Identifier Code. The standard was renamed because the code identifies financial and non-financial institutions alike, and plenty of BIC holders are not banks at all. Verified August 2026.

SWIFT itself is the organisation that operates the messaging network and acts as the registration authority for the standard. So SWIFT code and BIC describe the same string, one by the network that carries it and one by the standard that defines it.

What does each part of a SWIFT code mean?

A BIC is eight or eleven contiguous characters, with no spaces or punctuation, in four blocks. The standard's own names for those blocks are not the ones in common circulation, and knowing the real ones tells you what the code can and cannot do.

Only the country code means what its informal label suggests. The first and third blocks are simply prefixes and suffixes assigned to a business party, which is why you cannot reliably read a bank's name or a city out of them the way many guides imply.

The branch identifier is the block worth understanding operationally. It supplements the eight-character code to point at a specific location, department, service or unit of the same business party, and an eight-character code without it generally routes to the institution's primary office.

How is a SWIFT code different from an IBAN or a routing number?

They answer different questions. A SWIFT code says which institution. An IBAN says which account. A routing number says which domestic bank inside one country's clearing system. Confusing them is the single most common cause of a failed payroll file, because each field validates against a different format and a valid string in the wrong box passes the length check and fails the payment.

The IBAN check digits are the useful detail there. They are calculated so that a mistyped IBAN usually fails validation before the payment leaves, and SWIFT acts as the registration authority for national IBAN formats under ISO 13616. A SWIFT code has no equivalent self-check, so a wrong BIC can travel further before anything notices.

Not every country uses IBAN. The United States does not, which is why a payment from a US account to a European one needs a routing number at one end and an IBAN at the other, and a SWIFT code to connect them.

For the full set of details you need to collect before a first international pay run, check out our guide on How to Pay International Employees: A Complete 2026 Guide.

Where do you find a SWIFT code?

Get it from the account holder or their bank, never from a third-party lookup site. The recipient's online banking, a bank statement, or the bank's own published details are the reliable sources. Directory sites are frequently out of date after mergers and rebrands, and a stale BIC is one of the harder payment failures to diagnose.

For payroll specifically, collect it as part of onboarding and re-confirm it if an employee changes bank. The places it reliably appears are these:

• The recipient's online banking: usually under account details or international payment details.
• A bank statement: often printed in the header alongside the IBAN.
• The bank's own website: reliable for the head office code, less so for a specific branch identifier.
• Directly from the employee: the only source that also confirms the account is genuinely theirs.

That last point is a fraud control as much as a data-quality one. Bank details supplied by anyone other than the employee, or changed on the strength of an email alone, are the classic vector for payroll diversion, and the verification step costs a phone call.

Collecting and validating these fields is part of payroll processing rather than a one-off administrative task.

What does a SWIFT payment actually cost?

More than the fee you agreed, and you cannot know the total in advance. A SWIFT payment can be charged at four separate points, and only two of them are visible to the sender before the money leaves. This is the part that makes the rail awkward for payroll, and it is why an employee sometimes receives an odd amount nobody at your end can explain.

Row two is usually the largest single cost and the least discussed, because a rate margin does not look like a fee. Rows three and four are the ones that make the arriving amount unpredictable, since neither is under your control and neither is quoted to you.

You do get one lever. Most banks let you choose who bears the charges, and the three arrangements available are worth understanding before you set a default:

• Sender pays everything: the recipient receives the full amount, and you absorb the transit charges. The right default for salary.
• Charges shared: you pay your bank's fee and the recipient absorbs everything downstream. This is the common default and the usual cause of a short payment.
• Recipient pays everything: every charge comes out of the payment. Never appropriate for wages.

If you pay salaries by SWIFT, set the first option deliberately rather than accepting the second by default. An employee whose net pay arrives short by a transit fee has been underpaid in substance, whatever your bank's paperwork says, and fixing it after the fact costs more than the fee did.

The charge arrangement also interacts with how often you pay, since a fixed fee per transfer hurts far more on a weekly pay period than on a monthly one.

How long does a SWIFT payment take?

It varies, and the variation is the problem rather than the duration. A payment routed through a single correspondent can settle quickly, while one that passes through several, or that hits a compliance check, takes materially longer. We are not publishing a day range here because any number would be a generalisation across banks, corridors and currencies that we cannot verify for your case.

What matters for payroll is that the variance is not yours to control. Salary is a fixed-date obligation, so a rail whose arrival date moves by a day or two either forces you to send early or leaves employees waiting, and neither is a good answer to give repeatedly.

The factors that stretch the timeline are the number of correspondents in the chain, the currency corridor, cut-off times at each institution, weekends and public holidays at both ends, and any sanctions or anti-money-laundering screening the payment triggers.

This unpredictability is one strand of the wider global payroll complexity that grows faster than headcount does.

Teams that pay an offshore team every month usually abandon direct bank transfers for exactly this reason, not because of the headline fee.

Is SWIFT the right rail for paying an international team?

For a one-off payment, usually yes. For recurring salary, usually not. The characteristics that make correspondent banking universal are the same ones that make it a poor fit for payroll: it reaches almost any account anywhere, and it cannot promise an exact amount on an exact date.

The third row does something the first two cannot, and it is worth being precise about the difference. A payment rail moves an agreed amount. It does not decide what that amount should be after local tax and statutory contributions, and it does not make you a compliant employer in the recipient's country.

So the rail question and the employment question are separate. Sending a clean, exact transfer to someone who should have been on a local payroll solves the payment problem and leaves the compliance problem untouched.

For the delivery models available and what each one takes off your plate, read our article on Global payroll services: 2026 guide, costs & top providers.

Ask any candidate how they actually move the money and whether the recipient bears any deduction, which is the practical test when choosing a payroll provider.

If the people you are paying are contractors rather than employees, the reporting duties differ too, so check out our guide on How to Pay 1099 Employees: A Complete Employer Guide 2026.

This is one of the quieter arguments for payroll outsourcing: the provider already holds local banking relationships you would otherwise have to build country by country.

Bear in mind that moving the money is the last step, not the first, and the employer obligations sitting ahead of it are covered in our guide on Employer Payroll Taxes: The 2026 Guide for US Employers.

What goes wrong with SWIFT details in payroll?

Six failures account for most returned or short payments, and none of them is exotic. They are all data-quality problems, which means they are all preventable at onboarding rather than discoverable on pay day.

• Identifier in the wrong field: an IBAN entered as the BIC, or a routing number where a BIC belongs.
• A stale code after a merger: the bank rebranded, the BIC changed, and your record did not.
• The wrong branch identifier: an eleven-character code pointing at a branch the account does not sit in.
• A name mismatch: the account name not matching the employee record, which compliance screening will stop.
• The shared-charges default: salary sent with transit fees payable by the employee, so net pay lands short.
• Details changed by email: a bank-detail update accepted without verification, which is the standard payroll fraud route.

The fifth is the one that damages trust rather than just the payment run, because from the employee's side an underpayment looks identical whether the cause was a bank fee or a payroll error. Record the arriving amount, not the sent amount, when someone queries their pay.

Which is easier to settle when the statement itself is clear, so check out our guide on What Is a Pay Stub? A Complete Guide for Employers (2026).

It also matters that a transit deduction is not a payroll deduction: it happens after net pay was correctly calculated, so it never appears on the statement at all.

For the end-to-end sequence across several countries, read our article on How to Run Payroll for a Global Team: A Step-by-Step Guide.

When you compare routes on cost, count the transit deductions and the rate margin rather than the headline transfer fee, which is the same discipline that makes EOR pricing comparable against running payroll yourself.

The same rail questions apply to contractor payroll, with one difference: a contractor bears their own banking costs unless your agreement says otherwise, so the charge arrangement belongs in the contract.

For the operating routine that keeps bank details current and verified across a distributed team, check out our guide on Payroll Administration: What It Is & How to Manage It.

How does Wisemonk help global companies manage cross-border payments the right way?

Wisemonk is a leading Employer of Record (EOR) in India that helps global companies hire, pay, and manage employees, without setting up a local entity. We simplify complex HR operations so you can focus on strategy, not administration.

Here's how we help businesses manage cross-border payments more effectively:

• Legal employer of record: we act as your legal employer and manage payroll, taxes, and compliance under local employment laws.
• Local payment rails: salaries paid domestically in the employee's own country, so the exact amount lands on the expected date.
• One invoice, full visibility: you fund one payment and see exactly what reaches each employee, with no transit deductions to reconcile.
• Benefits administration: health insurance, retirement contributions and paid leave handled so employees stay satisfied and compliant.
• Fast, compliant onboarding: hire and onboard top talent in under a week, fully compliant with local labor and tax laws.

Currently we are strongest in India, and we are planning to expand into future markets such as the US and the UK. With Wisemonk, you get a reliable partner for your global hiring and payroll journey.

What our clients say

Companies from the US, UK, and Europe trust us to build their teams compliantly and fast. Here's what our clients say:

"I'm very happy that I discovered Wisemonk. They have been a pure pleasure to work with, and their attention to detail is impressive. They helped us understand their pricing model, find top-qualified individuals, interview them, and then onboard them. I gave them criteria for the type of people we sought, and they delivered. The individuals they were able to find have been some of the best engineers I have ever worked with. I recommend Wisemonk to anyone who is in need of staffing assistance."
- Dan Sampson, Head of Engineering at Cobu