SWIFT code

International bank identifier code used for cross-border wire transfers.

Definition

SWIFT code (Society for Worldwide Interbank Financial Telecommunication) is an 8-11 character identifier for a specific bank in international wire transfers. Required information for wires across borders.

Context

Delaware LLC US bank accounts have SWIFT codes for receiving international wires from home-country accounts or foreign clients.

Example

A founder wires $50K from their Dhaka bank account to their Mercury account to capitalize the LLC. The wire requires Mercury SWIFT code and the founder Dhaka bank SWIFT code.

Common pitfalls

Wire fees vary; international wires typically $25-50 per transaction.
Incorrect SWIFT codes cause wire failures and delays.

What a SWIFT code actually represents

A SWIFT code is the address of a bank, not the address of an account. When the glossary entry describes it as an 8 to 11 character identifier for a specific bank in international wire transfers, the practical takeaway is that the code points a payment network toward an institution and, in the longer 11 character form, toward a particular branch of that institution. The account number or routing number does the rest of the work of locating the exact account once the money reaches the bank. For a non-resident founder running a single member Delaware LLC, this distinction matters because people often confuse the SWIFT code with the account number and try to use one in place of the other. They are two different fields on a wire form, and both have to be correct for the transfer to land.

The structure of the code is fixed and readable once you know the pattern. The first four characters are the institution code, the next two are the country code, the next two are the location code, and the optional final three identify a branch. So a code that ends in XXX usually refers to the bank's primary or head office rather than a specific branch. Knowing this helps a founder sanity check a code before pasting it into a wire form. If a US bank gives you a code whose fifth and sixth characters are not US, something has gone wrong, because the country code segment must reflect the country where the receiving bank operates.

Because the SWIFT system is the messaging backbone that thousands of banks share, the code is less a piece of secret information and more a public routing label. A bank will publish its SWIFT code openly, and you can ask any support agent for it without hesitation. What stays private is the account number that sits behind it. Treat the SWIFT code as you would a street address that anyone can look up and the account number as the apartment number that narrows things down to your specific LLC balance.

BIC and SWIFT code are the same thing

One of the most common points of confusion for founders moving money across borders is the appearance of two different terms that mean the same code. SWIFT code and BIC, which stands for Bank Identifier Code, are interchangeable labels for the identical 8 to 11 character string. European banks and many fintech platforms tend to print the term BIC on their wire instructions, while US institutions tend to print SWIFT, and a founder seeing both on the same transfer can reasonably wonder whether two separate numbers are being requested. They are not. If a receiving bank gives you a BIC and a sending platform asks for a SWIFT code, you enter the same value in both places.

This overlap matters in practice because wire forms are not standardized across the world. A platform such as Wise might label the field BIC or SWIFT or even SWIFT or BIC together, while a home country bank in Dhaka, Lagos, or Manila might use yet another phrasing translated from a local language. The underlying data the network needs is constant even when the label on the screen changes. A founder who internalizes that BIC equals SWIFT will stop second guessing whether they are missing a field and will copy the same value with confidence wherever the wire instructions call for an institutional identifier.

There is a small wrinkle worth remembering. Some forms accept the short 8 character version and some require the full 11 character version. When a form rejects an 8 character code, appending XXX to reach 11 characters often resolves it, because XXX is the conventional filler that points to the head office. This is general information rather than a rule that holds at every bank, so confirming the exact expected length with the receiving institution avoids a rejected transfer.

Why this matters when you capitalize a foreign owned LLC

The glossary example describes a founder wiring 50,000 dollars from a Dhaka bank account to a Mercury account to capitalize the LLC. This is one of the first real money movements many non-resident owners make, and it is where the SWIFT code stops being an abstraction and becomes a gate that either opens or stays shut. Capitalizing the LLC means moving the owner's own funds into the company's US bank account so the business has working capital. Because the money is crossing from the founder's home country into the United States, the transfer rides the SWIFT network, and both the sending bank's SWIFT code and the receiving bank's SWIFT code have to be present and accurate.

For a single member LLC owned by one foreign individual, this capital contribution is also a bookkeeping event, not just a banking one. The wire that lands in the US account increases the owner's capital in the company, and that movement is the kind of related party transaction that later feeds into US reporting obligations for foreign owned single member LLCs. Keeping the wire confirmation, including the SWIFT details and the amount, creates a clean paper trail that supports the company's books and any later filing. The SWIFT code is the technical key that lets the money travel, and the documentation around it is what makes the transaction defensible on paper.

A founder should expect the first international wire to feel slower and more friction heavy than a domestic transfer. International SWIFT wires commonly settle in one to five business days rather than same day, and the sending bank may ask for the purpose of the transfer. Describing it accurately as a capital contribution to a US company the founder owns is straightforward and avoids confusion at the home country bank, which sometimes scrutinizes outbound transfers more than inbound ones.

How the SWIFT code fits into the formation timeline

A SWIFT code only becomes useful after the founder has reached a specific point in the formation sequence, so it helps to see where it sits in the chain. The journey usually starts with filing the Delaware Certificate of Formation, which carries a 110 dollar state fee, and then obtaining an Employer Identification Number by submitting Form SS-4 to the IRS. The EIN arrives free of charge and, for applicants without a US Social Security Number who must file by fax or mail, typically takes around 8 to 10 business days. Only once the company exists and has an EIN can the founder realistically open a US business bank account, and only once that account exists does the account's SWIFT code come into being.

This ordering catches some founders by surprise because they want to fund the company before everything else is in place. The reality is that the SWIFT code is downstream of formation and banking. There is no SWIFT code to receive a wire until a US bank or banking platform has issued the account. Platforms such as Mercury, Wise, Relay, Lili, and Payoneer each provide wire details once an account is approved, and those details include the SWIFT or BIC value the founder then shares with anyone sending money from abroad. Trying to collect a SWIFT code earlier in the process is simply premature.

Seen this way, the SWIFT code is a milestone marker. When a founder finally has it in hand, it signals that formation, the EIN, and account approval have all cleared, and the company is ready to receive its first cross border funds. It is a small string of characters that quietly confirms several earlier steps are complete, which is part of why founders feel a sense of progress the moment a banking platform displays it on the account dashboard.

A worked example of receiving a client wire

Consider a founder in Manila who runs a single member Delaware LLC providing design services to a company in Germany. The German client agrees to pay 8,000 dollars for a completed project and asks for wire instructions. The founder opens their Relay or Mercury dashboard, copies the account holder name as it appears on the account, the account number, the routing number, the bank's full mailing address, and the SWIFT code, and sends all of it to the client. The German client's bank uses the SWIFT code to route the message to the correct US institution and the account number to deposit the funds once the message arrives.

Because the sending side is in Europe, the client's bank may also ask the founder whether the US account has an IBAN. As the related glossary entry on IBAN notes, US accounts do not use IBAN, so the correct answer is that the founder supplies the SWIFT code plus the account number instead. Communicating this clearly upfront prevents the client's bank from stalling the transfer while it hunts for an IBAN that does not exist. A short note saying the account is US based and uses SWIFT rather than IBAN usually resolves the question in one message.

When the wire arrives, the founder should reconcile the deposited amount against the invoice, because international wires sometimes arrive slightly short. Intermediary banks in the SWIFT chain can deduct handling fees along the way, so an 8,000 dollar invoice might land as 7,960 dollars after a correspondent bank takes its cut. Knowing this in advance lets the founder either absorb the small difference or agree with the client on who covers wire fees, which is a normal commercial conversation rather than a sign that anything went wrong.

Intermediary banks and the correspondent chain

Behind a single international wire there is often more than one bank involved, and understanding this explains several otherwise puzzling outcomes. When the sending bank and the receiving bank do not have a direct relationship, the SWIFT message hops through one or more intermediary or correspondent banks that do maintain accounts with each other. Each of these institutions has its own SWIFT code, and occasionally the sending bank will ask the founder for an intermediary SWIFT code in addition to the receiving bank's code. The receiving bank, Mercury or Relay or whichever platform the founder uses, can supply the correct intermediary details when asked.

The presence of intermediaries is why an international wire can take several days and why the amount can shrink slightly between sending and receiving. Each correspondent bank in the path may levy a small handling fee, and these deductions are taken from the transferred amount rather than billed separately. This is distinct from the sending bank's own outbound wire fee and the receiving platform's inbound fee. For a founder, the lesson is that the headline amount and the landed amount can differ for legitimate structural reasons tied to how the SWIFT network is built, not because of an error in the SWIFT code itself.

Founders can reduce surprises by asking the sending party to use the OUR fee option where available, which instructs the sender to bear all charges so the full amount arrives. The alternative SHA option splits charges and BEN passes them to the receiver. These three letter codes appear on many wire forms and quietly determine who absorbs the correspondent deductions. None of this changes the SWIFT code itself, but it shapes how much money actually reaches the LLC's account.

Wire fees, FX spread, and the true cost of a transfer

The glossary entry notes that international wire fees typically run 25 to 50 dollars per transaction and warns that fees can hide inside the foreign exchange spread. Both points deserve unpacking for a founder who sends or receives money in a currency other than dollars. The visible wire fee is the easy part to budget for. The less visible cost is the exchange rate margin the bank applies when it converts, say, Bangladeshi taka or Philippine pesos into US dollars. A bank might advertise no transfer fee while quietly applying an exchange rate a percentage or two worse than the mid market rate, which on a large transfer can dwarf the flat wire fee.

This is one reason many non-resident founders favor platforms built around transparent currency conversion. A service like Wise tends to show the mid market rate and a separate stated fee, which makes the true cost legible rather than buried. When capitalizing the LLC or moving profits home, comparing the all in cost, meaning the flat fee plus the spread plus any correspondent deductions, gives a far more accurate picture than looking at the advertised wire fee alone. The SWIFT code is constant across these platforms, but the cost of using it varies a great deal.

For recurring international payments, small per transfer differences compound. A founder receiving monthly client wires of several thousand dollars each will, over a year, pay materially more through a high spread bank than through a transparent platform. None of this is a reason to avoid SWIFT wires, which remain the standard rail for large cross border sums, but it is a reason to treat the choice of sending and receiving institution as a cost decision rather than an afterthought.

How a wrong SWIFT code fails and how to recover

The glossary pitfall that incorrect SWIFT codes cause wire failures and delays understates how varied these failures can be, so it is worth describing the spectrum. In the cleanest case, an invalid code is rejected immediately because it does not match any registered institution, and the sending bank simply refuses to process the wire until it is corrected. This is annoying but harmless, since the money never leaves. The founder fixes the code and resends. This is the outcome to hope for when a typo slips through.

The harder case is a SWIFT code that is valid but wrong, meaning it points to a real bank that is not the founder's bank. Here the message and possibly the funds travel to the wrong institution, and recovery depends on that bank identifying the misdirected payment and returning it. This can take days or weeks and sometimes involves a recall request initiated by the sending bank. Because the code was structurally valid, automated checks do not catch it, which is why founders should copy SWIFT codes directly from their banking dashboard rather than typing them by hand or trusting a code remembered from a previous transfer.

Prevention beats recovery. Before a first wire with a new counterparty, sending a small test amount confirms the entire chain works without risking a large sum. Once a small transfer lands correctly, the founder can send the full amount with the same details. Keeping a single canonical copy of the LLC's wire instructions, including the exact SWIFT code, and sharing that same document with every payer reduces the chance that a manually retyped code introduces an error.

SWIFT, IBAN, and routing numbers compared

Founders frequently tangle three different identifiers that each solve a different problem, so a side by side comparison clarifies them. A routing number, also called an ABA number, is a nine digit code used inside the United States to identify a bank for domestic transfers such as ACH and domestic wires. A SWIFT code identifies a bank internationally for cross border wires. An IBAN identifies a specific account, mainly in Europe and some other regions, for international transfers. They are not substitutes for one another, and which ones you need depends on where the money is coming from and going to.

For a US based Delaware LLC, the typical pattern is clear. Money moving within the United States uses the routing number and account number. Money arriving from abroad uses the SWIFT code and account number, because US accounts do not have IBANs as the related glossary entry confirms. When the founder needs to send money to a European supplier or back to their own home country account, they will often need the recipient's IBAN and that recipient's SWIFT or BIC. Mapping each transfer to the right identifiers upfront avoids the back and forth that delays payments.

A simple mental model helps. Think of the routing number as the domestic version, the SWIFT code as the international bank locator, and the IBAN as the international account locator used in certain regions. The founder's US account exposes a routing number and a SWIFT code but not an IBAN. A founder who keeps this mapping straight will rarely be caught out by a wire form asking for a field their account does not have.

Banking platforms and the SWIFT details they provide

Each banking platform that serves non-resident founders surfaces wire details in its own way, and knowing where to look saves time. Mercury, Relay, Wise, Lili, and Payoneer all support receiving international wires and each displays the relevant SWIFT or BIC code somewhere in the account dashboard, usually under a heading like account details, wire information, or receive money. Some platforms partner with an underlying chartered bank, which means the SWIFT code shown belongs to that partner bank rather than to the fintech brand itself. This is normal and does not affect whether the wire reaches the founder's account.

Because the displayed bank name may differ from the platform's consumer brand, a founder should copy the exact account holder name, bank name, address, and SWIFT code as shown, without substituting the platform's marketing name. A client wiring money needs the legal banking details, not the app's logo name. When a founder mixes these up, for instance writing the fintech brand where the partner bank name belongs, the sending bank can flag a mismatch between the account holder and the bank, slowing the transfer while it verifies.

Founders sometimes hold accounts across more than one of these platforms to spread risk and to take advantage of different fee structures. In that situation each account has its own distinct SWIFT and account details, and confusing the wire instructions of one platform with another is an easy mistake. Labeling each saved set of instructions with the platform name keeps them straight, especially when invoicing different clients who may pay into different accounts.

Cross border money movement and US tax reporting

International wires into and out of a foreign owned single member LLC are not just banking events, they intersect with US reporting. A single member LLC owned by a non-resident is generally treated as a disregarded entity, and such an entity that has reportable transactions with its foreign owner is typically required to file Form 5472 together with a pro forma Form 1120. The capital contribution the founder wires in to capitalize the company, and any distributions wired back out to the owner, are exactly the kind of related party transactions this form is designed to capture. The SWIFT funded wire is the underlying transaction the paperwork later describes.

The stakes here are concrete. The penalty associated with failing to file Form 5472 when required is 25,000 dollars, which makes careful record keeping around every cross border wire more than a tidiness exercise. Saving each wire confirmation, with its date, amount, and SWIFT details, builds the documentation that supports the figures on the form. A founder who treats wire receipts as disposable can find it hard to reconstruct the year's related party transactions when filing time arrives. This is general information rather than tax advice, and the specifics of any individual filing are worth confirming with a qualified preparer.

It also helps to separate the banking question from the tax question in one's mind. The SWIFT code governs whether the money moves. The Form 5472 obligation governs how the movement is reported. A perfectly executed wire with a correct SWIFT code still needs to be recorded for reporting purposes, and a missed filing is not cured by the fact that the wire itself went through cleanly. The two run in parallel and both deserve attention.

Common misunderstandings founders carry into their first wire

Several myths circulate among first time non-resident founders, and clearing them up prevents avoidable mistakes. The first is the belief that a SWIFT code is private and should be guarded like a password. It is not. The SWIFT code is a public bank identifier that founders share freely on invoices and wire instructions. What stays private is the founder's personal login credentials and, to a lesser degree, the full account number, though even the account number must be shared with anyone who needs to pay the company. Treating the SWIFT code as secret only creates friction when clients legitimately ask for it.

A second misunderstanding is that the SWIFT code alone is enough to receive money. It is not. A wire needs the receiving bank's SWIFT code and the specific account number, plus the account holder name, to land correctly. Giving a client only the SWIFT code guarantees the wire cannot complete, because the network would know which bank but not which account. Founders should always send the full set of details together rather than assuming any single field suffices.

A third myth is that international wires are instant. Domestic US wires can settle the same day, but international SWIFT wires routinely take one to five business days because of time zones, correspondent banking, and compliance checks. A founder expecting an instant arrival may panic when funds do not appear within hours. Setting the expectation of a few business days, and checking with the receiving platform only after that window passes, keeps the experience calm and avoids unnecessary support tickets.

Edge cases that trip up otherwise careful founders

Beyond the routine wire, a handful of edge cases appear often enough to be worth naming. One is the rejected wire that bounces back days later minus fees. When a wire fails after partial processing, the returned amount can be smaller than the amount sent because intermediary banks already deducted their handling charges before the reversal. A founder who sent 5,000 dollars might see 4,940 dollars return. This is frustrating but mechanically normal, and it is another argument for sending a small test transfer first when working with an unfamiliar counterparty or a new SWIFT code.

Another edge case involves currency mismatches at the receiving end. If a client sends a wire denominated in euros to a US dollar account, the receiving bank converts it on arrival at whatever rate and margin that bank applies, which the founder does not control. The SWIFT code routes the message correctly regardless of currency, but the conversion can erode the value. Where possible, agreeing that the client sends in US dollars, or routing through a multi currency platform that lets the founder hold the foreign currency and convert on better terms, sidesteps an unfavorable forced conversion.

A third situation is compliance holds. Banks and fintech platforms run anti money laundering and sanctions screening on cross border wires, and a transfer from certain countries or above certain amounts can be held for review. The SWIFT code being correct does not exempt a wire from this scrutiny. When a hold occurs, the founder typically supplies documentation such as an invoice or a statement of the funds' purpose. Anticipating this for large transfers, and having supporting documents ready, shortens the delay.

Putting the SWIFT code in the wider banking picture

For a non-resident running a Delaware LLC, the SWIFT code is one component in a broader cross border banking setup rather than a standalone concern. It works alongside the routing number for domestic transfers, the account number that identifies the specific balance, and the wire details that platforms like Mercury, Wise, Relay, Lili, and Payoneer publish. Understanding how these pieces fit lets a founder confidently field a request from any payer anywhere, whether that payer asks for a SWIFT code, a BIC, an IBAN that the US account will not have, or a domestic routing number for a US based client.

It also sits inside the rhythm of running the company. The annual Delaware franchise tax of 300 dollars flat, due on the first of June, is paid from the same US account that the SWIFT code points to, and so are vendor payments and any distributions home. The account is the hub, and the SWIFT code is the international on ramp to that hub. A founder who set the company up through a one time 297 dollar formation package, secured the free EIN, and opened a banking platform account has, by the time the SWIFT code appears, assembled all the infrastructure needed to receive money from clients across the world.

One piece of good news for US formed LLCs concerns beneficial ownership reporting. Under the FinCEN Interim Final Rule of March 26 2025, domestic US formed LLCs are exempt from the beneficial ownership information reporting that once loomed over new entities. This does not touch the SWIFT mechanics directly, but it removes one compliance worry from the founder's plate and lets attention stay on the practical work of moving money correctly. The SWIFT code remains the small but load bearing detail that turns a US bank account into a globally reachable destination for the founder's revenue.

Related terms

Related glossary terms & guides

Form your LLC WhatsApp

WhatsApp Form your LLC