- A SWIFT code is a Business Identifier Code, not a Bank Identifier Code. ISO 9362 defines it, the name changed years ago, and it identifies a financial institution rather than an account.
- A SWIFT code runs eight or eleven characters in four blocks. A four-character business party prefix, a two-letter ISO country code, a two-character business party suffix, then an optional three-character branch identifier.
- The code routes the message while the IBAN identifies the account. A SWIFT code alone cannot deliver a payment, which is why payroll files fail validation on one field and not the other.
- Cost is the real payroll problem. Fees can be taken by the sending bank, by one or more correspondent banks in between, and by the receiving bank, and the sender cannot see the middle ones in advance.
Have questions about cross-border payments, or need help paying a team in another country? Reach out to us today!
Discover how Wisemonk creates impactful and reliable content.
Why does the same string of letters show up every time you send money abroad, and why does nobody explain what it actually costs you? A SWIFT code is a standardized identifier for a financial institution, and getting it right is the difference between a payment that lands clean and one that bounces or arrives short. For the wider picture of moving money to people in other countries, our global payroll guide covers the models around it.
This guide decodes the code against the standard that defines it, shows you what one looks like block by block, separates it from the identifiers it gets confused with, and then covers the part most explainers skip: what a SWIFT payment really costs.
What is a SWIFT code?
A SWIFT code is a standardized identifier for a financial institution, defined by the ISO 9362 standard. Its formal name is the Business Identifier Code, or BIC. 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. Under ISO 9362:2022 it is the Business Identifier Code, not the Bank Identifier Code. The standard uses that wording because the code identifies financial and non-financial institutions alike, and it applies to organizations rather than individual people.
SWIFT itself operates the messaging network and acts as the registration authority for the standard, which you can confirm on the SWIFT data standards pages. So SWIFT code and BIC describe the same thing, one named by the network that carries it and one by the standard that defines it. That single string is the first field a bank asks for when you set up any cross-border payment.
What does a SWIFT code look like?
A BIC is eight or eleven contiguous characters, with no spaces or punctuation, arranged 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 exactly what the code can and cannot do.
How are the four blocks structured?
Here is how the positions map, with the formal name and the informal label each block usually gets.
| Position | Length | ISO 9362 name | Commonly called |
|---|---|---|---|
| 1 to 4 | 4 alphanumeric | Business party prefix | Bank code |
| 5 to 6 | 2 alphabetic | Country code, per ISO 3166-1 | Country code |
| 7 to 8 | 2 alphanumeric | Business party suffix | Location code |
| 9 to 11 | 3 characters, optional | Branch identifier | Branch code |
Only the country code means what its informal label suggests. The first and third blocks are simply a prefix and suffix 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.
What does a decoded example look like?
A pattern makes it concrete. Take an illustrative eight-character code written as AAAA US NN: the first four letters are the business party prefix, US is the country code, and NN is the location suffix. Add an optional three-character branch identifier and it becomes eleven characters, AAAA US NN BBB, pointing at a specific office or unit of the same institution. An eight-character code with no branch block generally routes to the institution's primary office.
The branch identifier is the block worth understanding operationally, because an eleven-character code aimed at the wrong branch is a common reason a payment stalls. For most payees the eight-character head-office code is what you need, unless the recipient gives you a branch code tied to their account.
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.
Which identifier does what?
The quickest way to keep them straight is to compare what each one identifies and how it is built.
| Identifier | What it identifies | Structure | Standard or authority |
|---|---|---|---|
| SWIFT code, or BIC | The financial institution | 8 or 11 characters, four blocks | ISO 9362 |
| IBAN | The specific account | Up to 34 characters: country code, two check digits, then up to 30 more | ISO 13616 |
| US routing number (ABA) | The domestic US bank | Nine digits, an eight-digit routing number plus a check digit | American Bankers Association |
The IBAN check digits are the useful detail there. They are calculated so 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, with a SWIFT code connecting them. For the full set of details to collect before a first run, our guide on how to pay international employees walks through each field, and the net pay you promise is what these identifiers are meant to deliver intact.
Paying a team abroad without the SWIFT guesswork?
See what each person actually receives, and when, before you send. Wisemonk pays your team on local rails, so the exact amount lands on the exact date, with one funding instruction and full visibility.
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 the code at onboarding and re-confirm it whenever someone changes bank. These are the places it reliably appears, in rough order of reliability:
- 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 payee, or changed on the strength of an email alone, are the classic vector for payment diversion, and the verification step costs a phone call. Collecting and validating these fields is part of ongoing payroll outsourcing when you hand the function off.
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 a payee sometimes receives an odd amount nobody at your end can explain.
Where does the money get taken?
The four deduction points fall into two groups: the ones you can see before you send, and the ones you cannot.
| Deduction point | What is charged | Visible in advance? |
|---|---|---|
| Sending bank | An outbound international transfer fee | Yes, usually a published tariff |
| Currency conversion | A margin added to the exchange rate | Partly, rarely itemized |
| Correspondent banks in transit | A charge taken from the payment itself, possibly more than once | No |
| Receiving bank | An inbound or beneficiary fee | No, it depends on the recipient's bank |
The conversion margin is usually the largest single cost and the least discussed, because a rate margin does not look like a fee. The transit and receiving charges are the ones that make the arriving amount unpredictable, since neither is under your control and neither is quoted to you. A side-by-side on provider economics, like our Wise vs Payoneer comparison, shows how much the margin alone can move.
Who pays the charges?
You do get one lever. Most banks let you choose who bears the charges, and the three arrangements 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. 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. Someone whose net salary arrives short by a transit fee has been underpaid in substance, whatever the paperwork says. The deduction sits below the gross salary you agreed, so it never shows up as a payroll line, and it hurts far more on a weekly cycle than 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. Any single day range would be a generalization across banks, corridors, and currencies, so the honest answer is that you cannot promise an exact arrival date.
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 people waiting. 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 screening the payment triggers. This unpredictability is one strand of the wider complexity covered in our guide on how to run payroll for a global team.
Is it safe to share your SWIFT code?
Yes. A SWIFT code identifies an institution, not an account or a person, so on its own it reveals nothing that lets anyone move money out of an account. It appears openly on bank statements and bank websites for exactly that reason, and you share it every time you ask to be paid from abroad.
The real risk runs the other way. Fraud happens not when a genuine code is shared but when a fake set of details is slipped into your records, usually by an email asking you to update where a salary should go. The defense is to verify any change of bank details directly with the person, through a channel you already trust, before you touch the payroll record.
To keep the line clear, here is what is safe and what is not:
- Safe to share: the BIC itself, the IBAN or account number for receiving money, and the account name.
- Treat with caution: any request to change existing payment details, especially one that arrives by email alone.
- Never rely on: a third-party lookup site as your source of truth for someone's code.
The takeaway is that the code is not the sensitive part; the change process is. Build the verification step into onboarding and into every details update, and the most expensive payroll-fraud route closes for the cost of a phone call. Keeping these records current is a core piece of running global payroll at any scale.
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, but it cannot promise an exact amount on an exact date.
How do the main routes compare?
Comparing the routes on what payroll actually needs, an exact amount and a fixed date, makes the trade-off obvious.
| Route | Amount received | Arrival date | Best used for |
|---|---|---|---|
| SWIFT correspondent transfer | Can be reduced in transit | Variable | One-off or unusual-corridor payments |
| Local rail in the recipient's country | Exact | Predictable | Recurring payments at volume |
| Employer of record or payroll provider | Exact, net of correct statutory deductions | Fixed to the local pay date | Employing people, not just paying them |
The third row does something the first two cannot. 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 payee's country. So the rail question and the employment question are separate. When you compare providers, our guide on how to choose a payroll provider lists the right questions, and platforms such as those in our Gusto vs ADP comparison show how different the models can be.
If the people you pay are contractors rather than employees, the reporting duties differ too. Our guides on how to pay international contractors and how to pay 1099 contractors cover those, a contractor bears their own banking costs unless the agreement says otherwise, and in the US that pay is reported on Form 1099.
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.
These are the six that recur, in rough order of frequency:
- 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 payee record, which compliance screening will stop.
- The shared-charges default: salary sent with transit fees payable by the employee, so pay lands short.
- Details changed by email: a bank-detail update accepted without verification, the standard fraud route.
The short-payment case is the one that damages trust rather than just the 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, and remember that a transit deduction never appears on a payslip because it happens after net pay was correctly calculated.
A clear statement, explained in our guide to what a pay stub shows, makes these queries easier to settle, and solid contractor onboarding catches the data errors before the first payment.
How can Wisemonk help you pay a global team the right way?
Wisemonk is an India-native Employer of Record (EOR) provider that helps global companies hire, pay, and manage people without setting up a local entity. We see the consequences of broken cross-border payments every month: salaries arriving short, late, or failing validation. Here is how we take those failure modes off your plate, with the business problem each one solves.
- Acting as the legal employer: We become the registered employer for your hires, holding compliant contracts, tax registration, and statutory obligations, so you can engage talent you could not otherwise employ without your own entity. This removes the permanent-establishment and misclassification risk that a payment rail never addresses. Our guide on hiring international employees explains where that risk sits.
- Paying salaries on local rails: Instead of correspondent banking, we pay each person domestically in their own country, so the exact amount lands on the expected date with no transit deductions. This fixes the short-payment and variable-timing problems that make SWIFT a poor payroll fit, and it is the core of well-run global payroll services.
- Running managed payroll end to end: We handle gross-to-net calculations, statutory deductions, payslips, and the funding instruction, so you fund one payment and see exactly what reaches each person. This replaces the reconciliation headache of chasing deductions you cannot see, a routine we describe in our guide to payroll administration.
- Managing contractor payments: Where you engage contractors rather than employees, we coordinate compliant agreements and timely payment, with the charge arrangement written into the contract. This keeps a growing contractor base from becoming an untracked compliance and payment liability, as our guide on how to hire and pay international contractors explains.
- Administering benefits and ongoing compliance: We enroll your people in health cover and retirement contributions and keep filings current, so your team stays supported and your records stay audit-ready. This lifts the administrative burden that outlasts any single pay run, one of the clearest advantages of outsourcing payroll.
Taken together, these five services turn cross-border pay from a monthly reconciliation exercise into a predictable, compliant routine, which is the point of handing the function to a specialist rather than wiring money yourself. India is where we are strongest today. Employment, payroll, and compliance for your Indian hires are what we do best, and we are planning our expansion into markets such as the US and the UK.
Put your team on local payroll, not correspondent banking
If a wrong amount on the wrong day keeps happening, the rail is the problem. With Wisemonk as your employer of record, your people are paid the correct net amount on their local pay date, with compliance and benefits handled, and you get one invoice instead of a correspondent-fee puzzle.
What our clients say
Companies from the US, UK, and Europe trust us to build their teams compliantly and fast. Here is what two of them say about getting paid right:
"Wisemonk is a key partner for EOM-Energy O&M Services, playing an essential role in supporting our operations. Their seamless payment solutions make transactions not only simple and fast but also reliable. The team's responsiveness, professionalism, and proactive approach give us complete confidence in every interaction. We look forward to strengthening our collaboration, using Wisemonk both for Employer of Record services and for recruitment support, to help us expand our team in India in the short and medium term."
- José Enrique Montero Pérez, CEO at EOM-Energy O&M Services, USA
"We came across Wisemonk and met with the CEO and staff to explain our situation, and were very impressed with their customer-focused approach to their business. Wisemonk onboarded all of my employees in one or two days. They paid my employees' salaries on the day after my payment cleared. Needless to say, my employees and I were very satisfied with their service then and remain so over a year later. We are an American company, so I was very happy to see that they have a US bank account where I can make ACH payments to minimize bank charges. All salary payments are timely. They worked directly with my employees to enroll them in the health care program and explain any coverage-related issues. The best part is that we get to work with a dedicated person assigned to our company. I would highly recommend Wisemonk and think of them as our Indian HR department."
- Frank Menes, Founder & CEO at Senem RFP
Frequently asked questions
Is a SWIFT code the same as a BIC?
Yes, in everyday use they are the same thing. BIC is the formal term under ISO 9362, and SWIFT code is the common name, because SWIFT operates the network and acts as the registration authority. Banks print both labels interchangeably on statements and payment screens.
How many characters is a SWIFT code?
A SWIFT code is either eight or eleven characters. The eight-character form identifies the institution, its country, and its location. Adding an optional three-character branch identifier makes eleven. Both are valid, and an eight-character code usually routes to the institution's head office.
How do I find my own SWIFT code?
Check your online banking under account or international payment details, look at the header of a bank statement, or use your bank's official website. Avoid third-party lookup sites, which are often outdated after bank mergers and can send your payment to the wrong place.
Do you always need a SWIFT code to pay someone abroad?
Usually yes, if you send through the correspondent banking network. You do not need one if you pay through a local rail in the recipient's own country, which is how most payroll providers move money and why their fees and arrival dates are more predictable.
Why did a SWIFT payment arrive short?
Because fees were deducted along the way. A correspondent bank between the sender and recipient can take a charge from the payment itself, and the sender never sees that deduction in advance. The exchange-rate margin usually costs more than the visible fees combined.
Is it safe to give someone my SWIFT code?
Yes. A SWIFT code identifies a bank, not your account or you, and it appears openly on statements. The genuine risk runs the other way: accepting a change to payment details without verifying it, which is the main payroll-fraud route. Confirm any change directly with the person.
Is SWIFT the best way to run international payroll?
Rarely, for recurring salary. The unpredictable deductions and variable arrival times are tolerable for one-off transfers but poor for payroll, where people expect an exact amount on an exact date. Local rails or an employer of record handle recurring pay better.
Ready to build your India team?
Tell us who you're looking to hire. We'll walk you through exactly how the setup works for your company, your timeline, and your budget.