Kyriba vs Trovata: Which Fits a Mid-Market Group?

Kyriba vs Trovata is usually framed as old suite against new tool. That framing is accurate, and it leaves out what decides the choice for a UK or European group: how many banks you connect, which rails your payments run on, which ERP you close the books in, and where your data is allowed to live.

This comparison sets the two side by side on scope, price, implementation, connectivity and hosting, then gives a decision rule. We do not sell treasury software, so neither vendor is ours.

The short answer

• •Pick Trovata if your first problem is clean multi-bank cash visibility and forecasting, you run a handful of banks, and you want a price you can put in a budget before calling sales.
• •Pick Kyriba if you need a full treasury management system: FX and interest rate risk, debt, in-house banking, SWIFT and a long list of banks across many countries.

That matches the verdict in ai-toolfinder's October 2026 head-to-head: Trovata for US-centred companies that need cash data, forecasting and payments at a published price, Kyriba for global groups that need a full treasury system with risk management and broad bank connectivity. The "US-centred" part matters more than it looks, and we come back to it below.

Kyriba vs Trovata at a glance

Sources for each row are linked in the sections below.

Scope: a full treasury suite vs a cash platform growing a TMS

What Kyriba covers

Kyriba is the broader product by a distance: cash management, payments, bank and ERP connectivity, risk management across FX, debt, investments and interest rates, plus supplier and receivables financing. When General Atlantic invested in October 2024 it reported close to 3,000 customers in 170 countries and more than 3 billion bank transactions a year. Those are investor-announced figures and now two years old, so treat them as scale, not precision.

ERP Research's capability-level comparison makes the gap concrete. Of 33 capabilities where the two differ, Kyriba has stronger evidenced coverage on 27, led by liquidity planning, a centralised payment hub, SWIFT connectivity, payment fraud detection, FX hedging and hedge accounting.

What Trovata covers, and the ATOM caveat

Trovata leads on 6 of those 33, notably natural-language AI queries and rolling 13-week forecasts. Its roots are normalised bank data: balances, transactions, tagging, forecasting, cash positioning and reconciliation.

The full TMS is newer. Trovata announced the purchase of ATOM from Financial Sciences Corporation on 24 July 2025 and is rebranding it as Trovata TMS, covering debt and investments, intercompany, in-house bank support, FX hedging and bank account management. Per ai-toolfinder, integration is happening in two stages, grafting first and a full redesign second. If debt, derivatives or in-house banking are central to you, ask for references running Trovata TMS in production.

CFOpresso's review puts the same point plainly: Trovata is thinner on debt, investment and hedge accounting than legacy TMS, while Kyriba is overkill and hard to justify for most mid-market teams.

Price: one vendor prints a number, the other quotes

Trovata is one of the few treasury vendors with a public price. Its pricing page lists a base package at 24,000 USD a year with 1 bank, 100 accounts, 1,000,000 stored transactions and 10 users, including forecasting, cash positioning, reconciliation, payments, Trovata AI and 3 to 5 hours of live training. More banks, users, accounts and the TMS module are quoted separately.

Read the first line of that package twice. One bank. A UK group with a clearing bank in London, a euro bank in Frankfurt and a dollar account somewhere else is already outside the base price.

Kyriba publishes nothing. The only numbers in the public record come from Vendr, cited by ai-toolfinder: 50,000 to 150,000 USD a year for a mid-market core treasury deployment, plus a similar amount again to implement, with SWIFT connectivity, ERP integrations, data migration and support as the cost drivers. Kyriba has not confirmed those figures.

Subscription is rarely the number that surprises buyers. Concourse's cost breakdown notes that enterprise implementations can rival the first-year licence and consume hundreds to over a thousand internal IT and treasury hours. So compare the two on a three-year total: subscription, implementation, connectivity per bank, internal time and the renewal terms, in writing, at your real bank and entity count.

Implementation: weeks vs months

This is where the two diverge most. FintechSpecs' comparison describes Trovata's bank-connection-first rollout: two to four weeks to connect three to seven banks, then two to six weeks for ERP, tagging and reporting, so a lean team can reach a useful daily cash position in 30 to 60 days. Kyriba mid-market deployments run three to nine months in the same analysis, often with a systems integrator.

Trovata's own comparison datasheet claims 6 to 10 weeks against 6 to 10 months. That is vendor marketing from 2023, but it lands in the same range as the independent estimates.

FintechSpecs adds the cost nobody invoices: switching. Once your workflows and reporting are built on Kyriba's data model, leaving is a project. Trovata's API-based bank connections are lighter to unwind. Neither is a reason to choose on its own; both belong in the three-year model.

What a UK or European group should check first

Most of the content ranking for this comparison is written from a US buyer's seat. Three checks change the answer for a group run from London, Frankfurt or Amsterdam.

Bank connectivity and SWIFT

Kyriba states connectivity to 10,000+ banks over SWIFT, API and file channels. That breadth is built for exactly the European multi-bank estate: several banks, several countries, several file formats.

Trovata is API-first, with SWIFT access via Alliance Cloud. Its payments module runs on Real-time Payments, ACH and wire, which are US rails. CFOpresso's caveat applies directly: Trovata's value depends heavily on your banks being supported by its APIs. Before a demo, send Trovata your bank list and ask which connect natively, and how SEPA and Faster Payments are initiated.

ERP fit

ERP Research lists Kyriba's stated integrations as NetSuite, SAP, Workday, Oracle Fusion Cloud and Microsoft Dynamics 365, and Trovata's as NetSuite and Sage Intacct. If you are on SAP or Dynamics, that points to Kyriba. If you are on NetSuite, both are in play. Neither lists Xero, which a lot of UK groups close on, so ask both for a file-based or API route and who maintains it.

Where your data is hosted

Per ai-toolfinder, Trovata keeps customer data in the United States only, and Kyriba does not name its hosting region publicly. For European entities that is a check, not a verdict: put both questions to your data protection lead before signing. On security reports, Kyriba lists ISO 27001, SOC 1, SOC 2 and SOC 3 Type II; Trovata names SOC 2 Type II in its data processing addendum.

Which one to pick: a decision rule

If neither row fits cleanly, the shortlist is probably too narrow. Our ranking of the best treasury management software sorts the wider market by entity and bank count, and the Kyriba alternatives and Embat vs Kyriba comparisons cover the European mid-market options. If you are earlier than that, start with whether you need a treasury management system at all.

The layer underneath both

Kyriba and Trovata are both reading layers. They aggregate, forecast and initiate against accounts held somewhere else, and both price, one way or another, on how many banks they have to talk to. Fewer, better-structured accounts make either platform cheaper and simpler to run.

That is the part we build. EX FI provides multi-currency business payment accounts with dedicated IBANs in 16+ currencies, including GBP, EUR, USD, CHF and the Nordic currencies, on SWIFT, SEPA, FPS, BACS and CHAPS, with a Xero integration and intercompany payments between entities. It is not a TMS and does not replace either vendor. Regulated payment services are provided by Gemba Finance Limited (FCA FRN 804853), UK customers only. EX FI accounts are payment accounts, not bank accounts, and are not covered by the FSCS.

FAQ

Is Trovata cheaper than Kyriba? At entry, yes on the published numbers: 24,000 USD a year for Trovata's one-bank base package, against a Vendr estimate of 50,000 to 150,000 USD a year for mid-market Kyriba plus implementation. Each extra bank raises Trovata's price, so compare quotes at your real bank count.

Does Trovata have a full treasury management system? Yes. Trovata TMS came from the July 2025 ATOM acquisition and is quoted on request. It is newer inside Trovata than the cash product, so ask for production references if you need debt, hedging or in-house banking.

Does Kyriba or Trovata integrate with Xero? Neither lists Xero among its stated ERP integrations. Kyriba lists SAP, Oracle, NetSuite, Dynamics and Workday; Trovata lists NetSuite and Sage Intacct.

Is Trovata suitable for European entities under GDPR? Trovata hosts customer data in the United States only. That does not rule it out, but European entities should check it against their data transfer arrangements with their own data protection adviser before signing.