For most finance teams, month-end close is still a sprint. Not because anyone planned it that way — it just happens when you layer modern tools on top of a process designed for a paper-based world. Expenses trickle in at the last minute. Receipts are missing. Approvals sit in managers' inboxes while they're travelling. And the finance team ends up working weekends to make up the ground.

None of this has to happen. The businesses closing books fastest in 2026 didn't hire more accountants — they fixed the process architecture.

The actual problem

Month-end chaos is almost never a people problem. Finance teams are capable. The structural issue is that expense data is collected after the fact, approvals happen sequentially when they could run in parallel, and the finance team only discovers problems when they go looking at month-end. By then, the employee who made the purchase is three projects on and can't remember the details.

The fix is moving everything upstream. Capture data at the point of spend. Route approvals in real time. By the time month-end arrives, the accounting should already be done — the close is a review, not a recovery mission.

Receipt capture that doesn't require chasing

The most painful part of month-end isn't the accounting. It's finding the receipts. Employees lose them, forget to submit them, or submit them in the wrong format. The finance team sends reminder emails. The employee digs through their inbox. This repeats, across every team, every month.

The fix is to make receipt capture happen before the employee has time to forget. With Eduvo, every card transaction triggers a push notification within seconds of the purchase. The employee taps once, takes a photo, and it's done — still at the café, still at the restaurant, before they've walked out the door. If they don't respond within 24 hours, a reminder goes out automatically. Not from finance — from the system.

Teams using this consistently hit 97–99% receipt capture before month-end begins. Not because their employees are unusually conscientious — because the timing is right. Asking someone about a purchase the moment it happens is very different from asking them three weeks later.

Approvals that don't create a bottleneck

The second major problem is approval queues. An employee submits an expense, it goes into a queue, a manager reviews it when they get around to it (which might be days), and if there's a question it bounces back. Meanwhile, everyone waits.

Two changes fix most of this. First, set a threshold — say €250 — below which expenses are auto-approved if the category matches policy. Second, route anything above that threshold directly to the manager's phone for a 15-second decision. Approve or decline, add a voice note if context is needed. The decision is logged, timestamped, and auditable. No waiting. No email threads. No backlog at month-end.

Companies that do this report approval turnaround going from 3–4 days on average to under 2 hours. Over a month, that's the difference between expenses being current and expenses being a pile of unresolved claims the finance team has to sort through under time pressure.

GL coding at scale

One of the hidden time sinks in month-end is manual GL coding. Someone on the finance team reviews hundreds of transactions and assigns codes by hand. It's slow, error-prone, and — frankly — a poor use of the most qualified person's time in your finance function.

Modern platforms handle this with two mechanisms: merchant-level rules and AI-suggested categorisation. For recurring vendors — software subscriptions, regular suppliers, utilities — you set the GL code once and it applies automatically to every future transaction from that merchant. For one-off purchases, suggested categorisation reduces the job to reviewing a suggestion rather than creating one from scratch.

In practice, teams with this set up see 70–80% of transactions coded without human intervention. The remaining 20% are the genuine edge cases that always needed a human eye anyway. Finance ends up approving codes rather than assigning them — a fundamentally different job.

Multi-entity complexity

For businesses operating across multiple European markets — Spain and Sweden, say, or Denmark and the UK — month-end gets significantly more complicated. Intercompany charges, currency translations, different VAT treatment, different approval chains. The traditional answer is to collect reports from each entity and stitch them together at head office using spreadsheets and patience.

The better approach is a platform that handles the entity structure natively. Each entity operates in its own currency with its own approval chain, but all data flows into a single consolidated view. The CFO sees group-level spend in real time, with the ability to drill down by entity, currency, or category — without waiting for anyone to send anything.

What actually changes

Finance teams that close books fastest aren't working harder during close. They've front-loaded the work: expense data is clean before month-end starts, approvals are current, GL codes are assigned, currency calculations are already done. Month-end becomes a review process rather than a data entry sprint.

The time saving isn't marginal. Teams report going from 2–3 week close cycles to 3–5 days. Not because they found shortcuts — because they stopped building the problem into the process in the first place.

"Most finance teams don't need more people. They need a process that stops creating work at the worst possible time."

If your month-end still feels like a fire drill, the answer almost certainly isn't in the accounting. It's in how expense data gets captured three weeks earlier. Fix that, and the rest of the close follows naturally.

The average technology company in Europe pays for between 40 and 60 SaaS tools. Research consistently puts the unused or underused share at around 30%. That's a meaningful chunk of budget doing nothing — but the instinct to cancel everything is usually wrong. Cancel the wrong tool and a team loses a workflow they depended on, often spending more bringing it back six months later.

The smarter approach is targeted waste reduction. Here's how to do it without disrupting the teams who rely on what you have.

1. Get a complete picture first

The first obstacle to any SaaS rationalisation effort is that most companies don't actually know what they're paying for. Subscriptions hit shared cards, personal cards that get reimbursed, different department budgets. They accumulate over years. The real number is usually 20–30% higher than finance thinks.

The fix is to issue a dedicated virtual card per vendor — or at minimum, per category. Virtual cards from Eduvo take seconds to create, can be labelled by vendor name, and give you a clean, real-time map of every active subscription and its cost. When you want to cancel a tool, you freeze the card. No chasing login credentials, no navigating cancellation flows, no forgotten renewals continuing to charge after you thought you'd stopped them.

2. Set hard spending limits per tool

For tools with usage-based pricing — cloud infrastructure, API credits, seat-based plans that scale — spend can creep quietly until someone notices a bill that's three times last quarter's. The standard response is a post-mortem. A better response is prevention.

Setting a hard limit on a virtual card means that when a vendor tries to charge above your budgeted amount, the card auto-declines. You get notified immediately. The conversation happens before the damage, not after it. This works especially well for cloud providers, where a misconfigured environment can run up costs fast.

3. Consolidate overlapping tools — category by category

Most SaaS sprawl is the result of independent team decision-making over time. Marketing adopted one project management tool; engineering adopted a different one; customer success is using a third. Nobody coordinated. Nobody realised.

Go through your subscription list by category: video conferencing, project management, documentation, design, e-signature, customer communication. For each category, look at actual usage data — not what people say they use, but what the activity logs show. Pick one tool per category based on where the real usage is. The others go.

The savings from this step are often the largest of any initiative. The disruption is lower than expected if you give teams enough notice and handle the migration properly.

4. Move high-confidence subscriptions to annual billing

For tools you've used for over 12 months and expect to keep using, annual billing typically saves 15–25% over monthly. Review your monthly subscriptions and identify the ones where renewal is essentially a certainty. Move those to annual.

Be selective about this. Annual billing on a tool you cancel in month 4 is just a sunk cost. The right candidates are the tools that are deeply embedded in workflows — the ones where cancellation would require a major process change, not just switching tabs.

5. Add an approval step for new tool requests

The most effective long-term control isn't auditing what you already have — it's controlling what comes in. Most sprawl happens because anyone with a card can sign up for anything, and finance only finds out when they see the charge.

A lightweight approval flow changes this. Requests under €50/month are auto-approved if they're in an existing category. Anything above, or anything in a new category, needs a manager sign-off. The bar isn't high — you're not slowing anyone down significantly. You're just creating a moment of review and a paper trail before the commitment is made.

"The goal isn't to cut tools. It's to make sure every tool you pay for is being actively used by someone who genuinely needs it."

Combined, these five approaches typically reduce SaaS spend by 20–35% within a quarter. None of them require speculative cancellations — they're all based on real data, real usage, and real cost analysis. The teams keep what they rely on. Finance stops paying for what they don't.

Somewhere in Europe right now, there are thousands of startups sitting on seven figures of cash in current accounts earning essentially nothing. They raised a round, put the proceeds in the bank, and have been spending it down ever since — leaving the unspent portion completely idle.

This is understandable. Running a startup means constant demands on your attention, and optimising your cash balance rarely makes it to the top of the list. But the opportunity cost is real. And in the current interest rate environment, it's larger than it used to be.

What treasury trading actually means

Treasury trading, in a business context, means deploying idle cash into short-term, liquid financial instruments to earn yield while keeping the money accessible when you need it. The most common instruments are money market funds and short-dated government securities.

Money market funds hold a portfolio of short-term debt — government bonds, treasury bills, commercial paper — and pass the yield through to investors. They're designed to maintain a stable net asset value and offer daily liquidity. Short-dated government bonds (T-bills and similar) are direct obligations of national governments, typically with maturities between one week and twelve months. Both are considered low-risk by most institutional standards.

The goal is not speculation. It's not generating outsized returns. It's avoiding the situation where capital sits completely idle when liquid instruments can earn a meaningful return with minimal additional risk.

How it works mechanically

The traditional version of corporate treasury management required a treasury team, bank relationship managers, and a fair amount of paperwork. The modern version is largely automated.

You set a minimum operating balance — the amount you want to keep immediately available in your current account for payroll, supplier payments, and operational needs. Anything above that threshold is automatically allocated to treasury instruments. When your balance drops below the threshold because you've made a large payment, funds sweep back automatically.

Same-day liquidity is what makes this viable for startups. Unlike a fixed-term deposit, you can unwind your position and access the full amount any business day, without penalty or notice periods. That matters when your cash needs can be hard to predict six months ahead.

When does it actually make sense?

The honest answer depends on your cash position and company stage.

If you're pre-revenue with €200K runway, the yield on your treasury balance doesn't justify the management overhead. Spend your attention elsewhere.

If you're post-Series A, holding €2M or more in runway, and that cash is sitting in a current account, the calculation is different. At 3% annualised yield — a reasonable benchmark for short-term instruments in the current environment — €2M generates €60,000 per year. At €5M, that's €150,000. That's real runway extension without any additional revenue. It's worth understanding.

The inflection point is somewhere around €500K–€1M in cash. Below that, the absolute yield is unlikely to justify any meaningful management overhead. Above it, the question shifts from whether to do it to how to set it up efficiently.

The risk picture — be honest about this

Treasury products are investments, not deposits. This is an important distinction that matters both practically and in how you communicate it to your board.

Bank deposits up to €100,000 are covered by the European Deposit Guarantee Scheme. Money market funds and government securities are not deposits — they're investment products, and their value can fluctuate. In practice, the short-term, high-quality instruments used for corporate treasury have an excellent track record of stability and liquidity. But the risk is not theoretical zero, and you should be transparent about this with your board.

For most post-Series A companies, the relevant risk question is not "could I lose money?" (theoretically yes, practically very unlikely with conservative instruments). It's "could I lose access to this money when I need it?" With well-chosen liquid instruments, the answer is no — but do your homework on the specific product.

Common mistakes

Locking up too much. The point of treasury management is yield on your excess cash, not yield on all your cash. Over-allocating and then needing to unwind positions quickly to cover payroll creates unnecessary friction. Set a conservative minimum operating balance and stick to it.

Chasing yield into riskier instruments. Money market funds and short-dated government bonds are the appropriate instruments for most startups. Longer-dated bonds, credit products, or anything with meaningful duration or credit risk is a different conversation — one that requires more specialised oversight than most startup finance teams have capacity for.

Not telling your investors. Some term sheets or investor agreements include restrictions on how you hold cash. Check yours before setting this up. Most don't restrict it, but it's worth being certain — and even if there's no restriction, informing your board in advance is better than explaining it after the fact.

The practical starting point

For Eduvo Scale subscribers, treasury is available directly from your dashboard. You set your minimum operating balance, Eduvo automatically allocates excess to low-risk instruments, and funds are available same-day when you need them. There's no separate account to open, no relationship manager to call, no additional paperwork beyond initial setup. The yield accrues and is visible in the same dashboard as your current accounts and cards.

"Idle cash isn't a neutral decision. Leaving €3M in a current account for 18 months is a choice — and it has a real cost."

For the companies where treasury trading makes sense, starting is simpler than most people expect. The complexity that once surrounded corporate treasury management has largely been automated. The main thing standing between most startups and meaningful yield on their cash is simply the decision to start.

Starting today, all active Eduvo Scale plan subscribers receive a Metal Visa Infinite card as part of their account. It's heavier than our standard Business card, made from a stainless steel composite, and comes with a set of features designed for teams that travel frequently and spend at volume.

What the metal card includes

Worldwide airport lounge access is the headline feature. Cardholders and one guest can access over 1,300 lounges across 140+ countries through the LoungeKey network — Heathrow, Barajas, Gardermoen, Arlanda, Kastrup, and hundreds more. Access works through your Visa Infinite card number. No separate membership card, no per-visit fee.

The card earns the same Eduvo rewards as every other card in the platform. At each statement period, you choose: 0.5% cashback credited directly to your account balance, or 1 point per €1 spent, redeemable through the Eduvo travel and rewards portal. Rewards apply to all card spend, including flights and hotels booked through the Eduvo travel platform.

Visa Infinite also comes with elevated default spending limits and a higher contactless limit — relevant for high-value purchases and frequent business travel expenses that often bump against standard card limits.

What stays exactly the same

Your existing cards remain active. The metal card sits alongside your physical, virtual, and any other cards in your Eduvo account. Every spend control, budget limit, and approval workflow you've set up applies identically. Apple Pay and Google Pay work out of the box from the moment you add the card.

There's no separate app, no separate login, no separate statement. Transaction data flows into the same expense management dashboard as the rest of your company spend. The card is just a better version of what you already have.

Who gets it and when

Every active Scale plan subscriber is getting the metal card automatically — no action required. If you're already on Scale, your card is in production and will arrive within 5–7 business days. You'll get a push notification when it ships, with tracking details.

If you're on a Business plan and want to upgrade, the pricing page has the details. The upgrade takes effect immediately, and your metal card ships the same day your account moves to Scale.

"The metal card isn't a status symbol — it's what comes with Scale. The businesses using Scale at full capacity are already at the spending levels where lounge access and elevated limits make a real difference."

Questions about the card, lounge access, or the upgrade process? Reach out through the in-app support chat — the team is available 7 days a week.

Eduvo is now live in Norway. Norwegian businesses can open an account today and access the full platform: dedicated NOK IBAN accounts, Visa Business cards, SEPA and SWIFT payment rails, expense management with automated receipt capture, travel booking, and treasury trading for Scale subscribers.

This brings Eduvo to five European markets: Spain, the United Kingdom, Denmark, Sweden, and Norway.

What's available from day one

Norwegian businesses get the same platform as every other market — no feature gaps, no waiting list for specific capabilities. A NOK IBAN is issued on the same day as account opening, using Eduvo's direct banking infrastructure. Physical and virtual Visa Business cards ship within 2–3 business days. SEPA transfers are available immediately for EUR payments across Europe, and SWIFT payments go live on your first business day.

Expense management works for Norwegian teams the same way it works everywhere else on the platform: card transactions trigger receipt prompts via the mobile app, approvals route to managers based on your configured thresholds, and everything syncs with your accounting software. VAT treatment is handled correctly for Norwegian corporate tax purposes, and reports export in formats compatible with standard Norwegian accounting systems.

Why Norway fits the Eduvo model

Eduvo exists because European businesses operating across multiple markets still deal with unnecessary friction in their finance stack — multiple bank relationships, currency conversion fees on routine business purchases, and month-end reconciliations that take far longer than they should.

Norway sits squarely in that picture. Norwegian businesses frequently operate across Scandinavia, moving between NOK, SEK, and DKK regularly. Many have subsidiaries or key suppliers in the UK or continental Europe, requiring EUR payments as part of normal operations. Managing that through a single Eduvo account — with the right IBAN for each currency and cards that settle natively in local currency — removes a layer of operational friction that most Norwegian finance teams currently just accept as a fact of life.

"Five markets in just over a year. The goal was always to build the platform that European businesses actually needed — and that meant being present in the markets where they operate, not just the easy ones."

What comes next

We're not stopping at five. Our next market expansions will be announced over the coming months. If you're operating in a market we haven't reached yet, sign up at app.eduvo.io and we'll notify you when your market goes live.

Norwegian businesses can get started today. KYC takes around 10 minutes, and your NOK IBAN is ready the same day.

Running a business across multiple European markets sounds manageable until your finance team is reconciling expenses in four currencies, managing cards across two separate platforms, and trying to produce a consolidated month-end report that makes sense to your board. The spreadsheet grows. The manual steps multiply. And somewhere in that process, errors start appearing that nobody can trace back to their source.

Multi-currency expense management is one of the most consistently underestimated operational challenges for businesses scaling across Europe. This guide covers how to think about it structurally, and the decisions that create or eliminate overhead downstream.

The true cost of FX conversion

Most companies underestimate what they're actually paying in FX costs. The visible part — the fee shown on a bank transfer — is just one component. The larger and less visible cost is the exchange rate spread: the difference between the mid-market rate (the real interbank rate) and the rate your bank applies to the transaction.

A company processing €400,000 per month in cross-currency spend at a blended FX drag of 1.5% is paying €6,000 per month — €72,000 per year — in avoidable costs. That's before any explicit transfer fees. For a company with teams in the UK, Sweden, and Norway all using EUR cards for local purchases, this number accumulates quietly and rarely gets flagged until someone runs the analysis.

The fix is to transact in local currency wherever possible. A UK employee spending in GBP should use a card tied to a GBP account. A Swedish employee paying a Swedish supplier should pay in SEK from a SEK account. When you do this properly, the FX cost disappears — there's no conversion happening. Currency exchange becomes an intentional treasury decision, not an accidental byproduct of having the wrong account setup.

Account structure: the foundation

Multi-currency expense management starts with having the right accounts. The traditional approach for European businesses is one primary EUR account and a patchwork of workarounds for everything else — a separate GBP account at a different bank, SEK wired through an intermediary, NOK handled ad hoc. This creates multiple logins, multiple reporting formats, and a reconciliation challenge at month-end.

The modern approach is dedicated IBANs per currency on a single platform. EUR, USD, GBP, SEK, NOK, DKK, PLN, CZK, HUF, RON accounts all accessible from one dashboard, all visible in one consolidated view. When you have a GBP IBAN, UK customers pay you in GBP without sending an international transfer. UK suppliers get paid in sterling without conversion. UK payroll runs natively. The whole UK operation functions in its natural currency — and you make FX decisions once, when you repatriate profits or manage group cash, rather than on every individual transaction.

The same logic applies for each market. The goal is for currency conversion to be a deliberate treasury action, not an accident of having the wrong account type.

Card strategy across your markets

Cards are where a lot of FX leakage happens invisibly. An EUR card used by a UK employee for GBP purchases converts every transaction at whatever rate the card network applies that day. Over a month, for someone in a role requiring regular UK spend, the cumulative conversion cost is significant — and it shows up in the expense data as properly-categorised spend, so it's never flagged as an FX problem.

The right card structure depends on your headcount distribution. If you have meaningful employee populations in each market, issue local-currency cards tied to local-currency accounts: a GBP card for UK employees, SEK for Sweden, NOK for Norway. This eliminates conversion on everyday spend entirely.

For employees who move between markets regularly — a consultant who spends two weeks in London and two weeks in Stockholm — a multi-currency card that auto-routes to the right currency account handles it automatically. The card detects the transaction currency and pulls from the matching account. No manual management, no conversion fees on correctly-matched transactions.

Building a multi-currency expense policy

Single-currency expense policies don't translate directly to multi-currency operations. There are a few specific things that need to be defined explicitly.

Per diem rates vary significantly by country. What's reasonable for a night in Oslo is very different from what's reasonable in Madrid or Warsaw. Build country-specific per diems into your policy and apply them automatically based on where the employee is travelling, not where they're based. If your platform doesn't do this automatically, you end up with manual adjustments at every month-end close.

Reporting currency needs to be defined at the policy level. The standard approach is to report all expenses in your group base currency (usually EUR) at the mid-market rate on the transaction date — not the submission date or reimbursement date. This eliminates the FX variance that comes from timing differences between when a purchase happens and when it's processed, and keeps your GL accurate and consistent.

Intercompany charges deserve explicit attention. When one entity pays expenses that properly belong to another — a UK team member attending a Spanish client event and billing back to the Spanish entity — you need a defined charging mechanism, a clear intercompany FX rate, and a settlement cadence. These questions seem administrative until month-end, when they become the reason the books don't close cleanly.

VAT reclaim across borders

EU VAT is a meaningful financial opportunity that many multi-country businesses leave unclaimed. If a UK company sends employees to Germany or Spain, the VAT paid on hotel bills, conference fees, and certain business meals is often reclaimable under the EU VAT refund directive — but the mechanics are genuinely complex.

You need receipts that meet local VAT requirements (not all digital receipts qualify in all markets). You need to file refund claims in each relevant member state. The deadline for prior-year claims is September 30. And the value of individual claims often doesn't justify the time to file manually unless you've built a systematic process.

The practical solution for most companies is a VAT recovery service that handles the filing. The input is the same expense data you're already capturing: receipts, amounts, vendor details, transaction dates. If your expense capture is already clean and structured, the marginal cost of VAT reclaim is low. If your receipts are in a mess, fixing the underlying capture process is worth it both for the VAT reclaim and for everything else downstream.

Consolidated reporting that actually works

The CFO running a multi-country operation needs two views simultaneously: group-level consolidated spend in the base currency, and local-level analysis in local currencies.

Group-level view is how you spot anomalies at scale. A category that's 40% over budget across the whole organisation. An entity that's significantly behind on invoice processing. A travel cost trend building across markets that no individual entity's report makes visible. Without a real-time consolidated view, you're always looking at these things in retrospect.

Local-currency view is what makes the numbers meaningful to local finance teams and operating managers. Asking a Swedish finance manager to think about their operations in EUR introduces a constant mental conversion step — and it means FX rate movements show up as apparent budget variances even when nothing about the underlying operation has changed.

Both views are achievable, but they require clean underlying data. Currency metadata must be captured at the transaction level, not converted and discarded. The exchange rate used must be consistent (mid-market on the transaction date). And the data needs to flow into your reporting tool without manual steps in between.

The tech stack that makes this tractable

The stack that makes multi-currency expense management work without constant manual intervention has three components: a banking platform with local-currency IBANs and multi-currency cards; an expense management system that captures currency metadata and applies country-specific policies automatically; and a direct accounting integration that passes clean, categorised data to your GL without a CSV export in the middle.

When those three work together natively, month-end consolidation stops being a process and becomes a review. The data is already there, converted at the right rates, coded to the right GL accounts, split by entity. Finance's job is to check it, not build it from source data.

"The CFOs managing multi-currency operations most effectively aren't the ones with the biggest teams. They've eliminated the manual steps that create errors and eat time — and built a process where month-end is a review, not a recovery."

Getting this right is a design decision made early. The tools exist. The question is whether your account structure, card configuration, and expense policy have been built to eliminate FX friction at every step — or whether you're absorbing it, transaction by transaction, without fully accounting for the cost.

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.