Sweden’s Payment Backbone Is Changing: What CFOs, ERP Vendors, and Banks Need to Know

Sweden is sunsetting a big part of its payment infrastructure. Bankgirot services like supplier payments (Leverantörsbetalningar), salary runs (BG-Lön), and image-based reconciliations are being phased out. In their place? ISO 20022-based, bank-specific integrations.

Sounds simple on paper. It’s not.

What’s Actually Happening

By end of 2026, most corporate and ERP-initiated payment flows will need to bypass Bankgirot and go directly to each bank. Every bank is implementing its own version of payment formats, validations, and cutoffs. That means:

• File-based flows need to be rerouted
• New integration logic must be built
• Payment references, structures, and error handling change
• Reporting formats and reconciliation flows are disrupted

ERP vendors and corporates' finance teams are suddenly integration shops. Banks are suddenly service providers. Everyone is re-learning how to pay and get paid.

The Real Risk

When you split a unified flow into 10+ fragmented ones, bad things happen:

• Payments fail silently due to format mismatches
• CFOs lose real-time visibility across banks
• Reconciliation breaks
• Manual work creeps back in
• Financial ops teams burn out patching holes

The shift to ISO 20022 is not just a tech upgrade. It’s a financial control risk.

For Banks: Clients Will Choose Simplicity

If a client needs six different formats to initiate payments to six banks, they’ll consolidate business to the one that makes it easy.

Smart banks will:

• Offer white-labeled payment orchestration portals
• Work with API partners to normalize file intake
• Focus on insights and liquidity tools, not just pipes

If you’re a bank trying to keep your corporate base post-DCL, this is not just a format game. It’s a retention play.

For CFOs: Fragmentation = Blind Spots

Before: one channel, full visibility.
After: fragmented logic, missing balances, more errors.

Unless you rebuild:

• Central cash visibility across banks
• Real-time oversight of outgoing flows
• Integrated approval chains across entities and accounts

What used to be a finance dashboard becomes a series of spreadsheets overnight.

For ERP Vendors: This Is an Inflection Point

Rebuilding all these integrations internally is costly, error-prone, and distracts from your core product. It’s also likely to put you behind market expectations.

Option A: Maintain dozens of brittle, bank-specific flows. Hope they don’t break.

Option B: Partner with platforms that abstract this mess, validate flows, and return one normalized response.

You already know which is more scalable.

How Visualizy Helps

Visualizy is the control layer for this new world:

• One API, many banks
• ISO 20022 validation baked in
• Real-time cash visibility across fragmented accounts
• Secure, FS-approved workflows for approval and compliance

You focus on your finance operation. We handle the plumbing.

This shift is coming. It’s not optional.
‍

If you want to talk use-cases, pilots, or transition strategies, we’re here.

‍

‍

‍