SEPA vs SWIFT: which payment rail should your business use?

Two acronyms come up almost every time a European business talks about making payments internationally: SEPA and SWIFT. Most people have a rough sense that both are payment systems, but the details matter — and choosing the wrong one for a given payment either costs more than it should or introduces delays you didn't plan for.
Here's how each system works, when to use each, and how to think about the cost difference.
SEPA: built for Europe
SEPA stands for Single Euro Payments Area. It covers 36 countries: all 27 EU member states, plus Iceland, Liechtenstein, Norway, Switzerland, Andorra, Monaco, San Marino, and — importantly — the United Kingdom. The UK remained a SEPA member after Brexit, since SEPA membership is independent of EU membership.
The founding logic of SEPA was that cross-border EUR payments within Europe should work as smoothly and cheaply as domestic ones. For the most part, it delivers. A EUR payment from a Spanish company to a German supplier settles the same business day (for transfers sent before the daily cut-off) or next business day. Most European banks charge nothing, or a small flat fee, for SEPA credit transfers. There are no correspondent bank fees in the middle eating into the amount.
SEPA Instant Credit Transfer takes this further — funds arrive in under 10 seconds, 24 hours a day, including weekends and bank holidays. Not every bank supports it yet, but adoption has accelerated significantly in the last two years, and it's becoming the expected standard for EUR payments within Europe.
The constraint is clear: SEPA only handles EUR payments. A EUR payment from Denmark to Sweden settles via SEPA even if the Swedish recipient converts it to SEK on arrival. But a DKK payment to a Swedish supplier, or a NOK payment to a UK contractor, cannot use SEPA — those require a different mechanism.
SWIFT: global reach, different economics
SWIFT — Society for Worldwide Interbank Financial Telecommunication — is the messaging network that connects banks globally. Over 11,000 financial institutions in more than 200 countries use it. When your bank sends a SWIFT payment, it's instructing its correspondent bank (or a chain of correspondent banks) to move funds from one account to another. The actual settlement happens through those banking relationships.
SWIFT works for any currency, to almost any country. A EUR payment to a US supplier, a USD payment to a Canadian contractor, a GBP payment from France to a UK company — all of these go through SWIFT. It's the default for anything outside the SEPA zone or in a non-EUR currency.
The cost is meaningfully higher than SEPA. Your bank's outgoing wire fee (typically €15–40), potential correspondent bank fees in the middle (which can add another €10–25), and if there's a currency conversion, the exchange rate spread on top of that. On a €5,000 payment, the total friction can easily reach €40–70. For businesses making frequent international payments in non-EUR currencies, this adds up to a significant annual cost that rarely gets examined specifically.
Settlement time is also slower. Most SWIFT payments arrive in 1–3 business days for common corridors (US, UK non-SEPA, Asia-Pacific). Some destinations take longer, depending on the correspondent banking chain involved and whether the destination country has any additional compliance review requirements.
The simple decision framework
The choice between SEPA and SWIFT is mostly determined by two factors: geography and currency.
Use SEPA when you're sending EUR to any account in a SEPA country. This covers the vast majority of European supplier payments, EUR payroll, invoice settlements with European contractors, and intercompany transfers between European entities. It's faster, cheaper, and simpler than SWIFT for this use case — there's no reason to use SWIFT for EUR payments within Europe.
Use SWIFT when you're sending money outside the SEPA zone (the US, Asia, the Middle East, Africa, Latin America). Also use SWIFT for non-EUR currency payments to non-SEPA destinations — USD to US suppliers, SGD to Singapore contractors, and so on. And use SWIFT for GBP payments that are going through international routing rather than UK domestic rails.
GBP and other local currencies
The UK has its own domestic payment infrastructure that's worth understanding. Faster Payments handles GBP transfers between UK accounts and settles in seconds — it's the standard for GBP payments within the UK. CHAPS handles same-day high-value GBP transfers. For GBP payments to UK accounts, you'd use these domestic rails via a GBP IBAN rather than SEPA (which is EUR-only) or SWIFT (which is slower and more expensive for domestic GBP).
The same pattern applies across Scandinavia. SEK payments within Sweden use the local Bankgiro and Swish infrastructure. NOK payments within Norway use BankAxept and NICS. DKK payments within Denmark use Straksclearing. Cross-border payments in these currencies, or payments outside their home countries, typically route through SWIFT.
For businesses operating across multiple European markets, the practical implication is that you need local IBANs in each currency to access the domestic rails — not just a EUR account that converts everything. Without a GBP IBAN, your UK payments go via SWIFT instead of Faster Payments. Without a SEK IBAN, Swedish supplier payments go via SWIFT instead of the local domestic network.
The cost calculation over time
For occasional, large payments, the difference between SEPA and SWIFT is manageable. For high-frequency, regular payments — weekly contractor payments, monthly supplier invoices, fortnightly payroll runs — the cost differential compounds significantly.
A business making 40 international payments per month averaging €3,000 each, at a total SWIFT cost of €30 per payment, is spending €1,200/month — €14,400/year — on payment fees alone. If 60% of those payments could be restructured as SEPA (by invoicing in EUR or maintaining EUR accounts where appropriate), the saving on fees is around €8,600 per year. That's before the time cost of slower SWIFT settlement versus same-day SEPA.
"The rule is simple: EUR within Europe means SEPA. Everything else means SWIFT. Knowing the difference saves money every time you send."
Both SEPA and SWIFT are available from your Eduvo dashboard with no separate setup. SEPA transfers process same-day before the cut-off; SWIFT transfers initiate the same day and arrive within 1–3 business days depending on destination. Local currency rails for GBP, SEK, NOK, DKK, PLN, CZK, HUF, and RON are available through the corresponding IBAN accounts.