What Is International Wire Transfer: A 2026 Guide
Discover what is international wire transfer, how SWIFT and IBAN routing work, fees to expect, and tips for sending cross-border payments.
387.7 million commercial wire transfers originated from U.S.-domiciled accounts in 2021, with total value of $1,441.09 trillion. An international wire transfer is a bank-to-bank electronic payment instruction routed over the SWIFT network, and if you run a Bulgarian OOD or EOOD as a non-resident founder, this is the rail you'll often use when a German, French, or Dutch client pays you in euros and your bank needs to reconcile the money into your company account.
That's the simple version. The messy version is what founders deal with, bank details that must be exact, intermediary fees that can shrink the payment, and FX conversion that can change what lands in BGN or EUR.
If you've ever stared at an invoice from a EU client and wondered why the bank wants a SWIFT code, an IBAN, a purpose of payment, and sometimes a fee instruction, you're in the right place. The good news is that the process is straightforward once you know which parts are message, which parts are settlement, and which parts are just cost.
Table of Contents
- What an International Wire Transfer Actually Means
- How SWIFT, IBAN and Correspondent Banks Work Together
- Understanding the Full Cost: Fees, FX Markup, and Intermediary Charges
- Timings, Compliance and Common Reasons Wires Get Delayed
- Choosing Between SWIFT, SEPA, ACH and Fintech Rails
- Practical Tips for Bulgarian Company Founders and Freelancers
- Key Takeaways and Common Mistakes to Avoid
What an International Wire Transfer Actually Means
A founder in Sofia sends a €15,000 invoice to a German client, then waits to see whether the payment lands cleanly in the company account or gets slowed down by missing bank details. That's the everyday reality behind what people call a wire transfer, and it's why this rail matters so much for cross-border founders, freelancers, and SaaS teams.
The plain-English definition
An international wire transfer is a bank-to-bank electronic payment instruction that usually moves through the SWIFT messaging network instead of moving physical cash. The sender doesn't send a bag of money across borders, the sender sends a payment message that tells banks what to credit, where to route it, and how to settle it.
That difference sounds small, but it changes how you think about the payment. You're not shipping value physically, you're coordinating a chain of banks, account numbers, and compliance checks that ends in a credit on the recipient side.
For a Bulgarian company, that usually means a client in another country pays into your business account, the payment instruction travels through banking rails, and your local bank matches the incoming transfer to your legal entity and invoice data. If you're invoicing in euros, dollars, or pounds, the wire is the bridge between your foreign customer and your Bulgarian books.
Why founders use this rail
International wires are still one of the standard rails for cross-border payments, especially when the amount is significant, the payment needs to be reliable, or the counterparty expects a bank transfer rather than a card or wallet payment. The Federal Reserve's data shows that cross-border wires from U.S. accounts grew sharply from 2018 to 2021, with annual growth of 15.5% in number and 13.0% in value Federal Reserve payments data, which is a good reminder that this rail isn't niche.
For founders, the practical value is predictability. Banks know how to process it, accountants know how to reconcile it, and larger clients often already have approval workflows built around bank transfers.
The rest of the decision tree is simple. First, understand the rails. Then understand the data fields. After that, compare cost and timing, and finally decide when a wire is the right tool and when it isn't.
How SWIFT, IBAN and Correspondent Banks Work Together
A cross-border wire feels abstract until you treat it like a postal system for banks. SWIFT carries the message, the BIC identifies the bank, the IBAN identifies the account, and a correspondent bank steps in when the sender's bank and receiver's bank don't have a direct relationship.
SWIFT and BIC are the routing layer
SWIFT is the messaging network banks use to send payment instructions, not money itself. The BIC is the bank's unique identifier inside that network, so the sender's bank knows which institution should receive the instruction.
That matters because a wire is only as clean as its routing data. If the BIC is wrong, the instruction can stall before settlement even starts. If it's correct, the bank can move the message through the right channels and the payment has a clear path toward the beneficiary.
For Bulgarian founders receiving EU client payments, this is the part many people never see. The sender's bank may be in Germany, the receiving bank may be in Sofia, and the message still needs a unique route that banking systems can understand.
IBAN is the account destination
The IBAN is the recipient's standardized account number, and in the EU it does most of the heavy lifting for identifying where the money belongs. When the sender combines the IBAN with the BIC, they've given the banking system a complete destination.
That combo is why cross-border wires inside Europe are often easier to process than older, fragmented account formats. The receiving bank can map the instruction to the right account, then apply its own local settlement rules.
Practical rule: when the BIC and IBAN don't match the recipient's legal entity or account structure, expect delays, not miracles.
Correspondent banks handle the middle
A correspondent bank is an intermediary that helps one bank pay another when they don't have a direct relationship. In a USD to BGN payment, the transfer can hop through one or more correspondents before it reaches Sofia, and each hop can add processing time and fees.
That's why a wire can take longer than people expect. The sender sees a single action, but the banking system may be coordinating several institutions behind the scenes.
Before you send, the basic checklist is simple:
- Beneficiary full legal name, it needs to match the company or person receiving the payment.
- Bank name and address, so the instruction reaches the right institution.
- Account number or IBAN, this tells the bank where to credit the funds.
- SWIFT/BIC code, this routes the message correctly.
- Purpose of payment, often needed for compliance or accounting.
- Fee instruction, such as OUR, SHA, or BEN, if the bank asks for it.
If any of those fields is missing or wrong, the wire can be delayed, returned, or credited short. In practice, the data entry is half the job.
Understanding the Full Cost: Fees, FX Markup, and Intermediary Charges
A wire's visible fee is only the first layer. The amount that lands usually includes the sender's fee, intermediary charges, and the FX markup built into the conversion rate, so two payments with similar headline prices can arrive with different final amounts.
Bulgarian founders run into this fast. A client pays in euros, but the company account settles in another currency. A supplier invoices in dollars, and the bank converts on the way out. The invoice amount and the received amount can drift apart quickly when the route is indirect or the exchange rate includes a wide spread.
The three layers that matter
The first layer is the outgoing wire fee charged by the sending bank. In practice, that fee can range widely depending on the bank and the corridor, and some banks also charge for incoming wires on the other side.
The second layer is the intermediary or correspondent bank fee, which can be taken out along the SWIFT route. That charge does not always show up clearly on the sender's statement, which is why the recipient sometimes sees less than expected.
The third layer is the FX markup, the spread built into the exchange rate. Independent fintech guidance notes that these layers can make the transfer materially more expensive than the headline fee Melio international wire cost guidance. For founders comparing providers, a useful starting point is to compare the total cost stack, not just the fee shown at checkout, and FastCorp's pricing page can help frame that comparison for a Bulgarian company setup.
OUR, SHA and BEN in plain language
These fee instructions tell banks who should cover the charges.
- OUR means the sender covers the fees, which is useful when a Bulgarian company wants the recipient to receive the full invoice amount.
- SHA means the fees are shared, which is common but can leave the recipient short.
- BEN means the beneficiary pays, which is usually the least friendly option if you need a clean full-value receipt.
If you are collecting from a client and the contract says the payment must arrive in full, OUR is the clearest instruction. If you are paying a supplier and want to keep the invoice settlement clean, it often prevents back-and-forth about deductions.
Corridor choice changes the economics
The same wire can look cheap or expensive depending on the corridor. A USD to EUR transfer may appear simple at first, yet still carry FX spread and intermediary deductions. A USD to GBP or USD to INR wire can follow a different routing path, so the final landed amount can vary even when the send fee looks similar.
The wire fee is the easy part to compare. The hard part is the amount that actually lands.
If you are building a recurring payments process, compare the full stack, not just the initiation fee. That is the difference between thinking you saved money and saving money.
Timings, Compliance and Common Reasons Wires Get Delayed
A client payment can leave one bank quickly and still sit in transit for a few business days before it reaches a Bulgarian company's account. That gap exists because the wire passes through routing, screening, and settlement steps before the money is available to use. For a founder waiting on an EU invoice to close, the delay feels small on paper and very real in cash flow.
The impact usually shows up in bookkeeping first. If a payment lands later than expected, or arrives with a short amount or missing reference, invoice matching becomes harder and VAT reconciliation gets messy.
The checks banks run before release
Banks do more than send money from A to B. They check the sender and beneficiary details, screen the payment against sanctions lists, monitor transactions for unusual patterns, and keep records for compliance. That process is part of how international wires are handled under regulatory rules, including record retention expectations described in Wise wire transfer regulations.
For founders, that matters because the bank is not just looking for the right account number. It is also checking whether the payment fits what it expects from the customer, the corridor, and the stated purpose of the transfer.
The United States has reporting rules for large transfers, and the threshold often discussed in wire compliance guidance is payments of $10,000 or more, including related transfers that add up to that amount Wise wire transfer regulations. Other countries apply their own reporting rules, so a Bulgarian company handling cross-border receipts should keep transaction records organized even when the amounts are routine.
What usually slows a wire down
The delays are usually caused by small mistakes or normal banking cutoffs.
- Wrong BIC, the receiving bank cannot route the transfer cleanly.
- Missing IBAN, the account is not fully identified.
- Name mismatch, the beneficiary name does not match the account record.
- Cut-off time missed, the bank processes it on the next business day.
- Public holiday, one side is closed even if the other side is open.
- Extra documentation request, compliance wants more detail before releasing the funds.
A simple pre-check helps avoid most of these problems. Confirm the beneficiary name, IBAN, BIC, invoice reference, and payment purpose before sending, especially if the wire is going to a client, supplier, or tax-related account. Once the transfer is sent, reversing it usually takes more effort than catching the error at the start.
For founders who want the accounting side handled cleanly, FastCorp's accounting support can help match incoming wires to invoices, track FX differences, and keep VAT records in order.
Choosing Between SWIFT, SEPA, ACH and Fintech Rails
The right rail depends on where the money is going, what currency it's in, and how much control you want over cost and timing. For a Bulgarian founder, that usually means SEPA for euro payments inside Europe, SWIFT for broader global reach, and fintech rails when you care most about visible FX and simpler landing costs.
SWIFT is the global fallback
SWIFT is the default when the payment is large, time-sensitive, or outside the SEPA zone. It's built for reach, not for being the cheapest rail on the board.
That makes it useful for high-value B2B payments, treasury movements, and settlement with partners who want a bank transfer rather than a card or wallet. It's also the rail most founders mean when they say “international wire.”
SEPA fits euro payments inside Europe
If your Bulgarian company is getting paid by EU clients in euros, SEPA Credit Transfer is often the cleaner option. It's designed for euro payments within the SEPA area, which makes it a natural choice for most intra-European business flows.
The basic advantage is simplicity. The payment still needs accurate beneficiary data, but the routing is usually less complex than a global SWIFT chain.
ACH is a domestic U.S. rail, not a cross-border default
ACH belongs in the U.S. context. It's useful for domestic payroll and domestic vendor runs, but it doesn't solve the typical Bulgaria-to-EU founder problem on its own.
That's why so many cross-border explainers get confusing. They compare domestic U.S. rails against global rails as if they were substitutes, when they're really solving different problems.
Fintech rails can reduce invisible cost
Providers such as Wise, Airwallex, Revolut Business, and Mercury can sometimes deliver a better landed cost than a traditional correspondent chain because they pool liquidity and avoid some intermediary hops. Their appeal is not magic speed, it's better visibility into the full transfer cost and fewer hidden deductions.
For a founder, the decision rule is simple. Choose the rail that wins on corridor, currency, and amount, not the one with the prettiest fee banner. A cheap send fee doesn't matter if the FX markup and routing costs erase the savings.
Practical Tips for Bulgarian Company Founders and Freelancers
Bulgarian founders usually need three things at once, a bank account that can receive client payments, invoices that make the purpose of payment obvious, and bookkeeping that can survive VAT and tax filing. If those three don't line up, the wire itself may still arrive, but the admin around it turns into avoidable work.
Set the payment details before the client pays
When you invoice an EU client, the payment block should include the exact beneficiary name, the IBAN, the BIC, the currency, and a short payment reference that matches the invoice number. That gives the sender a clean path and gives your accountant something easy to reconcile later.
For founders setting up a Bulgarian company, FastCorp's company creation service can be one route for getting the legal entity, VAT setup, and banking support organized together. The useful part here is not the branding, it's the workflow, because the payment rail works better when the company structure and bank setup are already aligned.
Reconcile the wire the same day it lands
The moment an incoming payment hits the bank feed, match it against the invoice, check the FX difference if the payment was converted, and note any shortfall or intermediary deduction. If the amount doesn't match the invoice exactly, don't guess, document the gap and trace it back through the payment advice.
A clean audit trail matters because Bulgarian companies still need tidy records for VAT filings and annual corporate tax reporting. Bulgaria's 10% corporate tax regime makes the structure attractive, but the low tax rate doesn't reduce the need for disciplined bookkeeping.
If a client pays from abroad, the bank statement alone isn't enough. You still need the invoice, the payment reference, and the accounting note that explains any currency difference.
Compare banks on landed cost, not on account opening talk
A traditional Bulgarian bank may be comfortable for local operations, but an online EU IBAN provider can be easier for some founders who care about payment visibility and cross-border receipt flow. The key comparison is total cost of receiving, not just whether the account exists.
Ask two questions before you commit. First, what happens when the client sends euros and the account converts them later. Second, what happens if the bank deducts incoming fees or routes through correspondents. That's where the hidden leakage usually appears.
Automate the boring part
If your invoicing and bookkeeping tools can sync with the bank feed, reconciliation becomes a lot less painful. The goal is simple, make the incoming wire visible in the books fast enough that nobody spends half a day matching mystery receipts.
That's especially helpful for freelancers and agencies working with repeat EU clients. The more repeatable the process, the fewer payment errors you'll have to chase later.
Key Takeaways and Common Mistakes to Avoid
An international wire transfer is a bank-to-bank electronic payment instruction routed through SWIFT. For Bulgarian founders, it usually shows up in three places at once, receiving EU client payments, handling FX conversion, and matching incoming money to invoices and VAT records. The cost stack usually includes the send fee, any intermediary charges, and the FX markup. The timing is often 1 to 5 business days.
The mistakes are usually practical, not mysterious. A sender enters the wrong BIC, ignores intermediary fees, accepts a poor exchange rate from the sending bank, leaves out the payment purpose, treats a wire like a card payment that can be reversed on request, or forgets to record currency differences correctly in the books.
A helpful check is to read the transfer the same way an accountant would. What arrived in the bank account is only one part of the story. The invoice, payment reference, and accounting note still need to line up, especially if the wire came in a different currency or was routed through more than one bank.
FAQ
Can a wire be recalled? Sometimes, but only if the payment has not fully settled or if the banks can cooperate quickly. Once it has moved through the chain, a recall becomes difficult.
How long does a recall usually take? There is no single timetable, because it depends on where the payment sits in the routing chain and whether the recipient bank can return it cleanly.
What should I do if a wire arrives short? Check the fee instruction, the intermediary deductions, and the FX conversion first, then match the payment advice to the invoice before asking for a top-up.
Does a Bulgarian OOD or EOOD have to use SWIFT? No. For euro payments inside Europe, SEPA may be a better fit, and some fintech rails can be cleaner for certain corridors.
If you are setting up a Bulgarian company and want the banking, VAT, and bookkeeping side to work together instead of fighting each other, FastCorp can help you structure the entity, open the account, and keep the compliance flow organized. Visit FastCorp if you want a setup that is built for cross-border invoicing, EU payments, and clean reconciliation from day one.