Explainer

Kyriba explained: the cloud treasury platform, its owners and what implementation takes

Kyriba is one of the most common names on a UK treasury shortlist. This is what its four product areas do, who owns it, what drives the price, and the questions to settle before you sign.

By Christopher Fagan, Managing Partner, PEF Consulting Partners

19 yrssenior systems delivery
7finance platforms delivered
39 daysearly on an Oracle to Dynamics migration
22m+assets in the National Grid separation

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

Where Kyriba came from and who owns it now

Kyriba began in Paris in 2000 as a spin off from the French treasury software firm XRT, founded by Jean Luc Robert. It later incorporated in the United States and today lists San Diego as its headquarters, with a London office among nine international sites. Its chair and chief executive, Melissa Di Donato, joined in September 2023 and is based in London, which gives the UK business more senior attention than the head office address suggests.

Ownership is private equity. Bridgepoint, the London listed investor, first backed Kyriba and in October 2024 announced it would reinvest and stay majority shareholder, with General Atlantic joining as a minority investor. The deal valued Kyriba at more than three billion US dollars, and Bridgepoint said software revenue had tripled during its five years of ownership. At that point Kyriba reported close to 3,000 customers in 170 countries; its own company information page now claims more than 4,000 organisations and over 100,000 users.

Why this matters to a buyer: private equity ownership usually means sustained product investment and an eventual sale or listing. Neither is a reason to avoid Kyriba, but a contract that will outlast the current owner should protect you on price increases, data export and service levels if the business changes hands. For context on how Kyriba fits the wider market, read my guide to treasury management systems first.

The four product areas, and what sits inside them

Kyriba markets itself around liquidity performance, but the product breaks down into familiar treasury building blocks.

  • Treasury. Cash management and forecasting, advanced liquidity planning, in house banking, cash accounting, GL reconciliation, bank account management and bank fee analysis.
  • Payments. Core payment processing and a payment factory, a payment builder, netting, direct debits and SEPA mandates, plus payment anomaly and fraud detection and sanctions screening.
  • Risk management. FX exposure management on both balance sheet and cash flow, valuation, hedge accounting, EMIR reporting, credit risk, leases and market data, with position keeping sold separately.
  • Working capital. Supply chain finance on the payables side, dynamic discounting, receivables finance and supplier onboarding.

Around these sit connectivity services and analytics, and an AI layer Kyriba calls TAI, described as an embedded language model working inside the platform so customer data does not leave it. At its KyribaLive 2026 conference, the company announced direct access to J.P. Morgan Asset Management money market funds from inside the platform and an integration with Circle’s USDC for stablecoin settlement.

My practical reading: most UK buyers start with cash visibility, forecasting and payments, because that is where the daily pain is. Risk and hedge accounting matter if you run a material hedging programme under IFRS 9. Working capital finance is a different decision, often owned by procurement or the CFO, and I would not let it drive the treasury selection.

Who Kyriba suits, and where it is less natural

Kyriba says it serves companies from the mid market up to large multinationals, and its customer base bears that out. In UK terms, the strongest fit I would expect is a group with several entities, a dozen or more banking relationships, cross border payment flows and a small central treasury team that wants a SaaS platform rather than a system to host and upgrade.

It is a particularly natural candidate when payments and bank connectivity are the core problem. Kyriba says it connects to more than 10,000 banks through Swift, host to host links and bank APIs, and that it operates as a Swift service bureau. For a group trying to retire a tangle of bank portals and ERP payment files, that breadth is the main reason to look.

It is a less obvious first choice in three situations. A business whose treasury is dominated by commodity trading will find ION’s Openlink is built for that problem. A single entity UK company with two banks and no hedging probably does not need a dedicated treasury platform at all, and should look first at what its ERP cash management already does. And an organisation already committed to Coupa for spend may find Coupa Treasury easier to justify internally, even if Kyriba scores higher on paper.

Be wary of buying more product than your team can run. A three person treasury function can operate Kyriba well, but only if it picks the modules it will use in year one and adds others when the first set is stable.

How Kyriba prices

Kyriba does not publish prices. Its company information page describes the model as a modular subscription, paying for the capabilities you need, and directs buyers to a sales call for a quote.

In practice the quote is shaped by the modules you choose, the number of entities and bank accounts, the number of banks and the route used to connect to each, payment volumes, and the support tier. Kyriba offers Standard, Premium and Platinum support with follow the sun cover, and the difference between tiers is worth pricing explicitly because treasury outages at 9am are not something you want routed to a queue.

Three negotiation points I would raise. First, ask how bank connections are charged, per bank, per channel or within the subscription, because connection count tends to rise after go live. Second, ask how TAI and any future AI features are licensed, and whether today’s subscription includes them or whether they will become a separate charge. Third, cap annual uplifts for the full term, and make sure the cap survives a change of ownership.

Do not forget implementation costs, which sit outside the subscription. They are covered next.

ERP and bank integration

Kyriba lists prebuilt ERP connectors for SAP ECC, SAP S/4HANA, Oracle Cloud, NetSuite, Microsoft Dynamics 365, QuickBooks and Workday, and supports other ledgers through standard file and API protocols. It says it connects to more than 10,000 ERP instances. On the bank side, it offers bank reporting, Swift Business Connect, its Swift service bureau, and what it calls connectivity as a service.

The connectors are a starting point, not a finished integration. Each one still needs you to decide which ERP owns supplier bank details, how approved payables move into Kyriba, whether the ERP or Kyriba sends the final file to the bank, and how cash postings, fees, interest and FX revaluations return to the general ledger. Those choices decide where your payment controls actually live.

If you are mid way through an ERP move, align the two projects. A group moving to SAP S/4HANA should decide early whether SAP’s own cash and payment features or Kyriba will own bank communication, because building both and switching later costs time at the worst moment. The same applies on Workday Financials or NetSuite.

On security, Kyriba cites SOC 1 Type 2 and SOC 2 Type 2 reports, ISO 27001 and ISAE 3000, hosting on AWS and regional data residency options including the EU. Ask for the reports themselves, not the summary.

What implementation involves

Kyriba describes a phased method: strategic planning to agree scope and stakeholders, then bank and systems connectivity, testing and go live readiness, and adoption afterwards. It works with a network of consulting firms, naming Accenture, Deloitte, PwC, KPMG, Zanders, Clearsulting and Elire among them, alongside its own specialists. It gives no standard project duration, and I would distrust anyone who quotes one before seeing your bank list.

The critical path is almost never the software. It is bank onboarding: each bank has to set up the channel, agree formats and test payments, and that runs on the bank’s timetable. List every bank and account early, prioritise by payment value, and bring the long tail of small accounts in afterwards.

When I ran the procurement of every software provider on the National Grid separation, through to implementation, the lesson that carried across every package was simple. Contract for what you will actually deploy, write the bank and data responsibilities into the statement of work, and hold the integrator to named outcomes, not effort. That applies to Kyriba as much as to any ERP. Our project management service is built around those points.

The alternatives, and how to decide

The competitors you should test Kyriba against depend on your shape. ION’s Reval is the closest SaaS comparison for a growing team, with Wallstreet Suite for very complex treasuries. FIS Treasury and Risk Manager, now with a Quantum Cloud Edition, competes for larger enterprises with heavier risk needs. GTreasury, which Ripple agreed to buy in October 2025, is strong on risk and FX. Nomentia and TIS lead with payments and cash, and Coupa Treasury suits existing Coupa customers.

Run a scripted demonstration with your own banks, a real payment run and a real hedge, and ask each vendor to show what happens when a bank file is rejected. Check UK references of a similar size. Then compare five year costs on the same scope.

Our bench includes consultants who have led and analysed decisions before, during and after finance system migrations, and we take no fees or commissions from Kyriba or its rivals. If you want independent support through the choice, our fees are set out openly on the pricing page.

Related reading: Treasury management systems guide, BlackLine explained, Coupa explained, Accounts payable automation, Tipalti explained.

Common questions

What is Kyriba used for?

Kyriba is a cloud treasury platform used by finance and treasury teams to see cash across all banks and entities, forecast liquidity, run and control payments through a central hub, manage foreign exchange and other financial risk including hedge accounting, and run supply chain and receivables finance programmes. It connects to banks through Swift, host to host links and APIs, and to ERPs such as SAP, Oracle and NetSuite.

Who owns Kyriba?

Kyriba is privately owned. Bridgepoint is the majority shareholder after announcing in October 2024 that it would reinvest, and General Atlantic joined at that time as a minority investor. The transaction valued Kyriba at more than three billion US dollars. The company was founded in Paris in 2000, now lists San Diego as its headquarters, and its chair and chief executive Melissa Di Donato is based in London.

How much does Kyriba cost?

Kyriba does not publish prices. It sells a modular subscription, so the quote depends on the modules chosen, the number of entities, bank accounts and banks connected, the connectivity route, payment volumes and the support tier, with implementation services charged separately. Ask how bank connections and AI features are charged, and cap annual price increases for the full contract term.

Does Kyriba integrate with SAP and NetSuite?

Yes. Kyriba lists prebuilt connectors for SAP ECC, SAP S/4HANA, Oracle Cloud, NetSuite, Microsoft Dynamics 365, QuickBooks and Workday, and supports other ERPs through standard files and APIs. You still need to design which system owns supplier bank details, how approved payments flow into Kyriba, and how cash, fees and revaluation entries return to the general ledger.

What are the alternatives to Kyriba?

The main alternatives are ION Treasury, with Reval for growing teams and Wallstreet Suite for complex enterprises; FIS Treasury and Risk Manager; GTreasury, which Ripple agreed to acquire in October 2025; Coupa Treasury, built on BELLIN; and the payments led platforms Nomentia and TIS. The right comparison depends on your bank count, hedging activity, existing ERP and spend systems, and team size.

Weighing Kyriba against the rest of the shortlist? Share your bank list, entities and hedging activity and I will tell you where Kyriba fits and where it does not.

Book a confidential conversation

PEF TRACK RECORD£13bnLargestprogramme led5Continentsdelivered across19 yrsSystems delivery£25mLargestsingle saving
CF

Written by Christopher Fagan

Managing Partner, PEF Consulting Partners

Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.