Corporate Banking Software UK 2026: Bottomline, Kyriba, Open Banking, SWIFT

Corporate banking software addresses the operational reality that most UK businesses above a certain scale do not bank with a single institution. A mid-market group may hold accounts at three or four banks - one for working capital, one for treasury investments, one for FX-heavy international subsidiaries, and one for legacy reasons. Without dedicated software, managing these relationships creates duplicated effort, delayed visibility, and reconciliation errors that scale with transaction volume. This guide covers the corporate banking software landscape in the UK in 2026, the regulatory framework that has reshaped it (Open Banking and PSD2), and the selection criteria that should drive procurement decisions.

The UK Open Banking and PSD2 Framework

The most significant regulatory development in UK corporate banking software over the past decade has been the introduction of Open Banking, which began rolling out in 2018 following the Competition and Markets Authority's investigation into UK retail banking. Open Banking requires the nine largest UK banks to provide regulated third-party providers with access to account data and payment initiation services via standardised APIs, subject to customer consent. The framework is overseen by the Open Banking Implementation Entity (OBIE) and operates within the regulatory perimeter of the FCA.

The legislative basis for Open Banking is the second Payment Services Directive (PSD2), transposed into UK law as the Payment Services Regulations 2017 and retained in UK law post-Brexit. PSD2 created two new regulated activities: Account Information Services (AIS), which allow providers to aggregate account data from multiple banks into a single view, and Payment Initiation Services (PIS), which allow providers to initiate payments from a customer's bank account without using card networks. Both activities require FCA authorisation. The FCA's payment services framework sets out the conduct requirements for authorised providers.

For corporate banking software, this regulatory framework has democratised access to functionality that was previously available only through expensive direct bank integrations or SWIFT membership. Open Banking-enabled platforms can pull account data and initiate payments across multiple UK bank accounts with a single integration, dramatically reducing the technical cost of multi-bank cash management for growing businesses.

However, Open Banking does have limitations that matter for corporate users. The coverage is generally strongest for current account data; treasury products (term deposits, money market funds, FX positions) are often not accessible via Open Banking and require traditional bank-specific integrations. Payment initiation through Open Banking is typically limited to immediate payments rather than scheduled or batched payment runs, although this has been improving. International payments via Open Banking remain underdeveloped compared to SWIFT-based corporate payment infrastructure.

SWIFT Connectivity for International Corporate Banking

For UK businesses with international banking relationships, SWIFT connectivity remains essential. SWIFT (Society for Worldwide Interbank Financial Telecommunication) is the secure messaging network used by banks globally for cross-border payments, statements, and treasury communications. Direct SWIFT membership is impractical for most non-bank corporates due to cost and operational complexity, but several routes exist for corporate access.

SWIFT for Corporates (the Corporate Access programme) allows multinational corporations to connect to SWIFT through their banks via the SCORE (Standardised Corporate Environment) model. Treasury management systems (Kyriba, Bottomline, FIS) include SWIFT connectivity that consolidates multi-bank international relationships. Some FX platforms (Convera, Ebury) provide SWIFT-equivalent international payment capabilities without requiring direct SWIFT participation by the customer.

The choice between Open Banking-based domestic corporate banking and SWIFT-based international corporate banking is not binary - mature corporate banking platforms support both. For UK-only businesses, Open Banking-based platforms are typically sufficient. For UK businesses with international subsidiaries, suppliers, or customers, SWIFT-capable platforms are essential.

Leading Corporate Banking Software Platforms in the UK

Bottomline Technologies is one of the most established corporate banking software providers in the UK market. Its products cover payment initiation, fraud detection, and cash management for businesses across the size spectrum, from large SMEs to FTSE 100 corporates. Bottomline's Universal Approver and Payments and Cash Management platform integrate with major UK banks and support both Bacs and Faster Payments. The platform is widely deployed in UK local government, NHS Trusts, and large private sector organisations.

Kyriba is a treasury management system that has become a de facto standard for mid-market and large UK corporates with multi-bank, multi-currency, and treasury investment needs. Kyriba's strengths include bank account management, cash forecasting, and FX risk management - although it is positioned more as a treasury system than a pure corporate banking interface. For businesses with significant treasury activity, the lines between corporate banking software and treasury management software blur substantially, and Kyriba is competitive in both categories.

FIS Quantum (and FIS Integrity for smaller corporates) competes directly with Kyriba in the UK treasury and corporate banking software market. FIS has a strong installed base in UK financial services firms, public sector, and large corporates. Its SWIFT connectivity and multi-bank reconciliation capabilities are mature.

Yapily and TrueLayer are UK-founded Open Banking infrastructure providers that power many of the modern corporate banking and embedded finance applications used by UK SMEs. Both are FCA-authorised AISPs and PISPs. They are typically not deployed as end-user platforms but rather as the API infrastructure underlying other software (accounting platforms, expense management tools, payment apps). For businesses building custom internal tools that need bank connectivity, these are the primary options.

Bacs, Faster Payments, and CHAPS in Corporate Banking Software

UK corporate banking software must support multiple domestic payment rails, each with different use cases. Bacs Direct Credit handles bulk payment runs (payroll, supplier payments) on a three-day cycle and is the workhorse of UK corporate payments. Faster Payments provides near-instant payments up to a £1 million per transaction limit and has become the default for ad-hoc payments and many supplier payments. CHAPS handles high-value same-day payments and is used for property transactions, large supplier settlements, and treasury movements.

Pay.UK operates Bacs and Faster Payments. The forthcoming New Payments Architecture (NPA) will consolidate these systems, potentially affecting how corporate banking software interfaces with UK payment infrastructure. Businesses procuring corporate banking software in 2026 should ensure their chosen platform's roadmap addresses NPA migration without disruption.

Confirmation of Payee (CoP) is now standard across the UK banking sector. CoP checks that the name on the recipient's account matches the payment instruction before the payment is initiated, reducing authorised push payment (APP) fraud. Corporate banking software should expose CoP results to the user prior to payment authorisation. The Payment Systems Regulator's APP fraud reimbursement framework imposes liability allocation rules between sending and receiving PSPs for APP fraud losses, increasing the importance of robust CoP integration in corporate payment workflows.

Selection Criteria for UK Corporate Banking Software

Selecting corporate banking software is rarely just a feature comparison. The decision should hinge on bank connectivity (which UK and international banks the platform supports natively versus through generic Open Banking), payment volume capacity (does the platform handle your transaction volume without performance degradation), reconciliation automation (how well does it match incoming payments to invoices in your accounting or ERP system), audit trail and segregation of duties (especially for businesses subject to PRA or FCA supervision), and disaster recovery / business continuity (corporate banking is a critical function and platform outage tolerance is low).

For mid-market UK businesses, the trap to avoid is over-buying. Enterprise treasury platforms have impressive feature sets but require significant implementation investment and ongoing administration. A growing SME with three UK bank accounts and modest international activity is generally better served by an Open Banking-enabled platform that integrates with their existing accounting software than by a full treasury management system. The decision point typically arrives when international banking, multi-currency hedging, or intercompany lending becomes a material activity.

FAQ

What is the difference between Open Banking and SWIFT?

Open Banking is a UK and European framework for third-party API access to retail and SME bank accounts, primarily for domestic use cases. SWIFT is a global interbank messaging network used for cross-border payments and corporate banking communications. Open Banking is regulated by the FCA in the UK; SWIFT is a Belgium-based cooperative. For UK-only domestic banking, Open Banking-based platforms are typically sufficient. For international banking, SWIFT connectivity (directly or via a treasury platform) remains the standard.

Is Open Banking secure enough for corporate payments?

Open Banking uses strong customer authentication (SCA) and OAuth-based consent flows that meet the security requirements of the Payment Services Regulations 2017. The same regulatory framework that governs Open Banking governs the wider UK payment services market. For high-value or sensitive transactions, additional controls (segregation of duties in the corporate workflow, two-factor approval, payment limits) are best practice regardless of whether the underlying rail is Open Banking-based or traditional.

Do I need a treasury management system, or is corporate banking software enough?

The distinction blurs at the mid-market level. Corporate banking software typically focuses on payment initiation, account aggregation, and reconciliation. Treasury management systems add liquidity forecasting, FX risk management, intercompany lending, and investment portfolio management. If your business has multiple currencies, hedging activity, or intercompany cash pooling, you need treasury functionality. If your needs are limited to UK current account operations and payment processing, corporate banking software is sufficient.

How does Confirmation of Payee affect corporate payment workflows?

Confirmation of Payee checks the recipient's account name against the name provided in the payment instruction before the payment is sent. For bulk payment files (payroll, supplier runs), CoP checks may be performed at file upload or per-payment. Corporate banking software should surface CoP mismatches clearly and require user confirmation before proceeding. This adds friction but materially reduces APP fraud risk, particularly in scenarios where supplier bank details may have been compromised by an attacker.

What FCA permissions does a corporate banking software provider need?

A corporate banking software provider that initiates payments on behalf of customers needs Payment Initiation Service Provider (PISP) authorisation. A provider that aggregates account data needs Account Information Service Provider (AISP) authorisation. A provider that only acts as a passive interface to the customer's own bank-issued credentials may not require FCA authorisation. The FCA Register lists authorised PISPs and AISPs; check provider authorisation before contracting.

How We Verified

This article draws on the FCA's payment services framework and AISP/PISP authorisation guidance, the Payment Services Regulations 2017 as published on legislation.gov.uk, the Open Banking Implementation Entity's published documentation, and publicly available product documentation from corporate banking software providers referenced. Regulatory positions reflect the framework as of May 2026. Verify any specific functionality directly with vendors before procurement.

Sources

• FCA - Payment Services and E-Money Regulations
• Payment Services Regulations 2017 - legislation.gov.uk
• PSR - Authorised Push Payment fraud framework
• Bank of England - Payment and settlement systems