IBAN (International Bank Account Number)

Standardized account number format used in international wire transfers, especially in Europe.

Definition

IBAN is a standardized account number format (up to 34 characters) used for international wire transfers, primarily in Europe and some other regions. Combines country code, check digits, and bank-specific account information.

Context

Required for wires to/from European accounts. US accounts do not use IBAN; use SWIFT plus account number.

Example

A Delaware LLC receives a wire from a European client. The client needs the LLC bank info (no IBAN since US-based); the LLC needs the client IBAN for return transactions.

Common pitfalls

US accounts do not have IBANs.
IBAN format varies by country (length, check digits).

What an IBAN actually represents in a payment instruction

An International Bank Account Number is a single string that encodes everything a foreign bank needs to route money to one specific account. Reading it from left to right, the first two letters name the country where the account is held, the next two characters are check digits that let software validate the number before any money moves, and the remaining characters carry the domestic account information in whatever shape that country uses. The country code follows the ISO 3166 standard, so DE points to Germany, FR to France, GB to the United Kingdom, and AE to the United Arab Emirates. The check digits are not random. They are calculated with a modulo 97 formula that catches the most common human errors, such as two transposed digits or a single mistyped character.

For a Delaware LLC owner who has spent years inside a European or Gulf banking system, the IBAN feels like the normal way to identify an account because that is how local transfers are addressed at home. The mental shift that matters for a US company is that an IBAN is a regional convention rather than a global one. It tells a sending bank not only which institution to credit but also enough internal detail to land the money in the right account without a separate account number field. That bundling is why the string is long and why pasting it correctly matters so much.

Understanding the structure helps a founder reason about errors instead of guessing. If a payment is rejected and the message mentions an invalid check digit, the problem is almost always a typo in the string itself rather than a closed account or a compliance hold. Knowing which part of the IBAN means what turns an opaque failure into something a founder can diagnose calmly before contacting either bank.

Why a US-based Delaware LLC sits outside the IBAN system

The United States never adopted IBAN, so a Delaware LLC banking with a US institution or a US-based fintech does not receive one. This is not a gap in the account or a sign that something is missing. American banks identify domestic accounts with a routing number and an account number, and they identify themselves to the rest of the world with a SWIFT or BIC code. When a founder opens an account with a provider that runs on US rails, the account simply lives in a different addressing scheme than the one used across Europe.

This becomes a practical issue the first time a European client or supplier asks the LLC for its IBAN. The honest and correct answer is that the company does not have one because it is a US entity. What the client actually needs is the bank name, the SWIFT or BIC code, the US account number, and often the bank physical address and the ABA routing number. Many European payment portals include a field for these details precisely because they expect to pay counterparties that operate outside the IBAN zone, even if the IBAN field looks mandatory at first glance.

A founder who internalizes this avoids a frustrating loop where a client insists on an IBAN, the founder asks the US bank for one, and the bank explains that no such number exists. The smoother path is to send the client the SWIFT-based details up front, framed as the US equivalent of the IBAN, so the payer can complete the international transfer without back and forth that delays the very first invoice.

How IBAN relates to SWIFT in a single transfer

It helps to think of SWIFT and IBAN as answering two different questions inside one payment. The SWIFT or BIC code answers which bank, and the IBAN answers which account at that bank. In the IBAN world the account string usually carries enough information that the SWIFT code is paired with it for cross-border routing, while inside the United States the SWIFT code is paired with a plain account number instead. A wire leaving a European account for a US Delaware LLC therefore uses the sender IBAN on one side and the recipient SWIFT plus account number on the other.

This asymmetry is the core of why founders get confused. A transfer is not IBAN-to-IBAN or SWIFT-to-SWIFT. It is whatever each side natively uses, stitched together by the correspondent banking network. The European payer identifies their own account with an IBAN, and they identify the Delaware LLC with SWIFT details. The two formats coexist in the same instruction without conflict because the network was built to translate between regional conventions.

When a founder later needs to send money the other way, perhaps refunding a client or paying a contractor in the IBAN zone, the roles flip. The Delaware LLC supplies its SWIFT-based US details as the source and collects the recipient IBAN as the destination. Storing both the SWIFT details and any counterparty IBANs in a clean reference document saves time, because most disputes and delays trace back to one side using a stale or mistyped identifier.

A worked example: receiving a first European invoice payment

Imagine a founder in Lisbon who has formed a single-member Delaware LLC for a software consulting business and opened an account with a US-based provider such as Mercury or Relay. Their first real client is a marketing agency in Amsterdam that agrees to pay a 4,000 euro project fee. The agency finance team opens its banking portal, reaches the international payment screen, and asks the founder for an IBAN. The founder, knowing the US has none, instead sends the bank name, the SWIFT code, the account number, the bank US address, and a note that the account is denominated in US dollars.

The agency enters those details in the non-IBAN fields of its portal and initiates the transfer. Because the payment crosses from euro into dollar, an exchange happens somewhere along the path, and a correspondent bank may deduct a fee before the money lands. The founder should expect the deposited amount to differ slightly from a naive euro-to-dollar conversion of 4,000 euro, since the spread and any intermediary charge come out of the transferred sum. None of this involves an IBAN on the receiving side.

A week later the founder over-delivers and the agency wants to send a small bonus, but this time the founder also needs to refund an unrelated overpayment to a different Dutch vendor. For the refund the founder reverses direction and uses the vendor IBAN as the destination, supplying the LLC SWIFT details as the source. The same project, viewed across two transfers, shows how the LLC is always the SWIFT side while the European counterparties are always the IBAN side.

Where IBAN fits in the formation-to-banking sequence

IBAN questions do not arrive until fairly late in the setup journey, which is worth keeping in mind so a founder does not chase banking details before the company legally exists. The sequence usually starts with filing the Certificate of Formation with the Delaware Division of Corporations for the $110 state fee, which brings the LLC into existence. After that comes the federal Employer Identification Number, obtained for free by filing Form SS-4, which typically takes around 8 to 10 business days for a foreign founder without a US Social Security number to receive.

Only once the LLC has both its formation document and its EIN can it realistically open a US business account, and only after that account exists does the question of how Europeans will pay it become concrete. At that point the founder discovers there is no IBAN to give out and learns to lead with SWIFT details instead. Slotting IBAN literacy into this stage, rather than treating it as a formation-time concern, keeps the founder focused on the actual blocking steps in the right order.

It also clarifies which costs belong to which phase. The $110 formation fee and the free EIN are formation costs. The banking relationship and any wire fees, often in the range of $25 to $50 per international wire on the sending side, are operating costs that begin once money starts to move. The IBAN versus SWIFT distinction is purely an operating concern that surfaces with the first cross-border invoice.

Choosing a banking partner with cross-border payments in mind

The providers that non-resident founders commonly use, including Mercury, Wise, Relay, Lili, and Payoneer, differ in how they present international receiving details, and that difference shapes the IBAN conversation. Some of these are US banks or banking platforms that give the LLC a US account number and SWIFT code with no IBAN at all. Others operate multi-currency accounts and can issue local receiving details, sometimes including an IBAN-style number tied to a European entity, which lets a client pay as if sending a domestic transfer within the IBAN zone.

Wise in particular is known for multi-currency receiving details, so a Delaware LLC using it may be able to hand a European client a euro account number that looks and behaves like a local one. This can lower the client friction and the per-transfer cost compared with a pure cross-border SWIFT wire. The trade-off is added complexity in how those balances map back to the LLC books and tax reporting, since the underlying account may sit with a partner entity rather than the US bank the founder thinks of as their primary account.

There is no single correct choice here, and the right fit depends on where the LLC clients are concentrated and how often money crosses currencies. A founder serving mostly US clients may never need anything beyond a SWIFT code, while a founder invoicing across the eurozone might value receiving details that spare clients the cost and unfamiliarity of an outbound international wire. The point is to understand what each provider does with international addressing before committing, rather than discovering the limitation during a payment dispute.

IBAN, currency conversion, and the cost of cross-border money

An IBAN by itself says nothing about currency. A German IBAN identifies an account that almost certainly holds euro, but the IBAN is just an address. The real cost in cross-border payments comes from the exchange between currencies and from the fees that banks along the path deduct, not from the format of the account number. A Delaware LLC founder who fixates on the IBAN question can miss that the larger financial impact is the spread applied when euro becomes dollar.

When a European client pays a US LLC, the conversion can happen on the sending side, in the middle, or on the receiving side, and where it happens affects who controls the rate. If the client converts to dollars before sending, the LLC receives a clean dollar figure but the client bore the spread. If the money travels as euro and converts on arrival, the receiving provider sets the rate and may take a cut. Knowing this lets a founder decide whether to invoice in dollars, in euro, or in a multi-currency setup that holds the original currency until the rate is favorable.

Intermediary or correspondent bank fees add another layer. A traditional SWIFT wire can pass through one or more correspondent banks, each of which may deduct a charge, which is why a payer who sends an exact invoice amount sometimes results in the LLC receiving slightly less. This is general information about how cross-border transfers behave and not a prediction of any specific fee, since charges vary by bank, route, and currency pair.

Common misunderstandings founders carry from home banking

The most frequent misunderstanding is the belief that every legitimate business account in the world has an IBAN. Founders from IBAN-heavy regions often assume that a US account without one is somehow incomplete or that they opened the wrong product. The reality is that the US chose a different addressing standard, and a perfectly functional Delaware LLC account simply uses routing and account numbers domestically and a SWIFT code internationally.

A second misunderstanding is treating the IBAN as a secret like a password. An IBAN, like a SWIFT code and account number, is shared with anyone who needs to pay the account, and disclosing it for the purpose of receiving funds is normal and expected. The sensitive credentials are the login details and any authorization codes, not the receiving identifiers printed on an invoice. Founders sometimes hesitate to share US banking details out of an instinct carried over from guarding their IBAN, which slows down getting paid.

A third is assuming that because a client demands an IBAN, the LLC must acquire one or open a European account. In most cases the client portal accepts non-IBAN details once the founder points to the correct fields, and only a founder with genuine, recurring eurozone collections needs to consider a multi-currency receiving setup. Reacting to a single demanding client by restructuring banking is usually an overcorrection rather than a necessity.

Edge cases: rejected payments and validation failures

Because the IBAN carries its own check digits, many errors are caught before money moves, which is a feature rather than a frustration. If a founder enters a counterparty IBAN to send a refund and the portal rejects it with a validation error, the cause is almost always a mistyped character. Re-reading the IBAN against the source and confirming the country code and length for that country usually resolves it. IBAN length is fixed per country, so a number that is too short or too long for its country code is invalid on its face.

Other edge cases are more subtle. A payment may pass IBAN validation yet still fail because the account is closed, the name on the transfer does not match the account holder, or a compliance screen flags the transaction. These failures have nothing to do with the IBAN format and instead reflect the realities of cross-border money movement, including sanctions screening and anti-money-laundering checks that scrutinize first-time transfers between new counterparties. A founder should not assume a format problem when the IBAN itself validated cleanly.

On the receiving side, the LLC may occasionally see a wire bounce back because the sender entered the SWIFT code or account number incorrectly, the mirror image of an IBAN typo. The remedy is the same kind of careful comparison against the canonical details. Keeping a single authoritative copy of the LLC SWIFT details, and reusing it rather than retyping, prevents most of these reversals and the lost days they cause.

Documentation and records around international transfers

Every cross-border payment a Delaware LLC sends or receives generates a record that matters for bookkeeping and for tax reporting, and IBAN-addressed transfers are no exception. A foreign-owned single-member LLC files Form 5472 along with a pro forma 1120 to report reportable transactions between the company and its foreign owner or related parties, and the penalty for failing to file is $25,000. Capital contributions, loans, and certain payments between the founder and the LLC can be reportable, so the wires that move money across borders are exactly the events that need clean documentation.

This makes the habit of saving transfer confirmations more than housekeeping. When a founder wires startup capital from a home-country account into the LLC, that inbound transfer is the kind of related-party transaction that informs the 5472 filing. The IBAN of the founder personal account, the date, the amount, and the dollar value credited should all be retained. The same applies to any money the LLC sends back to the owner. Treating each cross-border movement as a documented event keeps the annual filing straightforward.

None of this is tax advice, and the precise reporting treatment of a given transfer depends on facts a founder should confirm with a qualified preparer. The general principle worth carrying is that international transfers and the IBAN or SWIFT details attached to them are part of an audit trail, not isolated banking actions. Building the record-keeping habit early means the founder is not reconstructing a year of transfers under deadline pressure.

The Delaware franchise tax and why banking readiness matters

Delaware charges most LLCs a flat $300 annual franchise tax, and it falls due on June 1 each year regardless of whether the company earned anything. This is a fixed obligation tied to keeping the entity in good standing, and it has to be paid from somewhere, which is one practical reason a founder wants a funded and functioning account before the date arrives. A founder who is still wrestling with how a European client can pay them may find the franchise tax deadline approaching with no easy way to cover it.

The connection to IBAN is indirect but real. If the LLC primary inflows come from eurozone clients, the founder needs a reliable way to convert and hold dollars so the $300 can be paid without scrambling. A founder who has sorted out whether to invoice in dollars or to use multi-currency receiving details will have predictable dollar balances available when the franchise tax and any registered agent renewal come due. Banking friction left unresolved tends to surface at exactly these fixed deadlines.

Planning a small dollar buffer in the account covers the $300 franchise tax and recurring service costs without forcing a poorly timed currency conversion. The IBAN versus SWIFT mechanics are upstream of this, since they determine how smoothly money arrives in the first place. A founder who treats getting paid and meeting Delaware obligations as one connected system, rather than two separate problems, avoids the predictable June cash crunch.

How IBAN connects to compliance: BOI, EIN, and entity status

Founders sometimes conflate banking identifiers with regulatory filings, so it is worth separating them clearly. An IBAN or its US SWIFT equivalent is a payment address and carries no regulatory weight by itself. The compliance obligations that attach to a Delaware LLC are distinct, including obtaining the EIN through Form SS-4 and meeting federal reporting such as the Form 5472 mentioned earlier. Banks will ask for the EIN and formation documents when opening an account, but they do so to satisfy their own know-your-customer rules, not because the IBAN system requires it.

On beneficial ownership reporting, the landscape changed with the FinCEN Interim Final Rule of March 26, 2025, under which US-formed LLCs are exempt from filing beneficial ownership information. A single-member Delaware LLC formed in the US therefore does not face a BOI filing obligation under that rule. This matters to the banking picture only in the sense that founders no longer need to fold a BOI step into their setup checklist, freeing attention for the practical work of getting accounts and payment details right.

The takeaway is to keep three buckets separate in one mental model. Formation creates the entity, federal filings like the EIN and Form 5472 handle tax reporting, and banking identifiers like SWIFT or IBAN handle money movement. A founder who blends these together tends to over-worry about the wrong thing, such as treating a missing IBAN as a compliance gap. Each bucket has its own rules, and the IBAN question lives squarely in the money-movement bucket.

Related terms that sharpen the IBAN picture

Several adjacent concepts make the IBAN clearer by contrast. The SWIFT or BIC code is the closest relative, since it is the identifier a US Delaware LLC uses in place of the IBAN structure that European accounts rely on. Where the IBAN bundles bank and account into one string, the US approach splits them into a SWIFT code plus a separate account and routing number. Understanding one makes the other easier to use, which is why these terms travel together in any cross-border payment.

Correspondent banking is the invisible machinery that lets an IBAN-addressed account and a SWIFT-addressed account exchange money at all. When no direct relationship exists between the sending and receiving banks, a correspondent bank in the middle bridges them, and its presence explains both the time a wire can take and the fees that may be deducted along the way. A founder who knows this stops blaming the IBAN or SWIFT detail for delays that actually come from the routing in between.

Multi-currency accounts and local receiving details round out the picture. These let an LLC hold or receive funds in euro, pounds, or other currencies, sometimes with an IBAN-style number attached, which can reduce the friction of pure cross-border wires. Knowing these options exist gives a founder a vocabulary for asking providers the right questions, rather than accepting that a US account can only ever receive money the hard way.

Putting IBAN knowledge into a repeatable invoicing routine

The lasting value of understanding IBAN for a non-resident founder is a calm, repeatable routine for getting paid across borders. The routine starts with a single saved block of the LLC receiving details, which for a US account means the bank name, SWIFT or BIC code, account number, routing number, and bank address, with a clear note that there is no IBAN because the account is US-based. Sending this block proactively with every international invoice removes the most common stall before it happens.

When a client portal insists on an IBAN field, the founder responds by directing the client to the international or non-IBAN section of the form and supplying the SWIFT details there. If the founder serves enough eurozone clients that this friction recurs, that is the signal to evaluate a multi-currency provider that can offer local receiving details, weighed against the added bookkeeping it introduces. The decision is driven by volume and currency mix, not by any single client preference.

Finally, the founder folds each transfer into the record-keeping habit that supports Form 5472 and clean year-end accounting, saving confirmations for both inbound capital and outbound payments. Combined with a dollar buffer for the $300 Delaware franchise tax due June 1, this turns the once-confusing IBAN question into a settled part of running the company. This is general operational information rather than legal or tax advice, and a founder with a complex setup should confirm specifics with a qualified professional.

Related terms

SWIFT code

Related glossary terms & guides

Form your LLC WhatsApp

WhatsApp Form your LLC