Kyriba Pricing in 2026: What a TMS Actually Costs

Kyriba is one of the most capable enterprise treasury management systems on the market, and one of the least transparent about what it costs. There is no public price list and no self-serve tier. Every deal runs through sales, which makes Kyriba pricing hard to plan around before you are already deep in a procurement cycle. This guide pulls together what real contracts and third-party trackers actually show, so you can size a Kyriba deal before you talk to a rep.

A note on sourcing: because Kyriba publishes no pricing, every figure below is a third-party estimate from a named tracker or review site, not from Kyriba, and the ranges are wide because the cost scales with your size. Treat them as directional, and lead with the two sources backed by real contracts (SpendHound and Vendr) over the illustrative range tables.

How much does Kyriba cost?

Kyriba pricing is quote-based and scales with your number of entities, bank connections, and modules. Based on real contracts tracked by SpendHound, smaller and mid-market teams pay roughly $62,000 per year on average and enterprises roughly $337,000 per year, while Vendr puts the median annual deal near $75,000. Implementation and professional services typically add another $50,000 to $150,000, per itqlick.

If cost is what is pushing you to look, Concourse is the AI-agent alternative. Instead of a heavy enterprise TMS, Concourse connects to your existing ERP, data warehouse, and banking data and runs treasury workflows end to end, with scoped pricing and a fast, forward-deployed implementation rather than a months-long rollout.

How Kyriba pricing works

Kyriba is sold as a modular SaaS subscription, quoted per deployment. There is no per-seat list price. Instead, the number is built from a few components that stack up:

• Modules. The base is Cash and Liquidity Management, with Payments and Connectivity, Risk Management, and Working Capital or Supply Chain Finance added on. Each module you turn on raises the subscription.
• Scale. Pricing scales with your number of legal entities, bank accounts, and bank connections, plus transaction volume.
• Connectivity. SWIFT and bank-specific connectors are typically billed on top of the base subscription.
• Commitment. Contracts are commonly multi-year and billed annually, with discounts for longer terms and larger deployments.

Because the price is assembled this way, two companies of similar revenue can get very different quotes depending on how many banks, entities, and modules they need. That is also why the public estimates span such a wide range.

Kyriba subscription cost estimates

The most credible figures come from sources tracking real, anonymized customer contracts. SpendHound reports an average of roughly $62,000 per year for small and mid-market customers (a small sample, so treat it as directional) and roughly $337,000 per year for enterprise customers. Vendr puts the median annual deal near $75,000, with observed deals ranging from about $24,000 to $96,000.

Worth flagging: the observed-deal figures (a ~$75,000 median, ~$96,000 top end) sit well below the quoted enterprise range tables ($350,000 to $1,000,000+). Those are two different things. The observed deals skew toward smaller, core-treasury implementations; the six- and seven-figure numbers are illustrative ranges for large, full-suite global rollouts. Do not average them, and expect your own quote to depend heavily on entity and bank count.

Implementation and professional services

The subscription is only part of year one. Implementation and professional services are a separate, significant line. itqlick puts Kyriba implementation and professional-services costs in the $50,000 to $150,000 range for a typical deployment, and notes Kyriba claims prebuilt bank links can cut that by over half. For larger, multi-entity rollouts, third-party estimates run higher, into the $200,000 to $500,000+ range.

Kyriba also sells professional services as prepaid "Value Added Services Packages," bundles of PS hours that, per its own fact sheet, do not roll over and expire after 12 months. The rates are not published. Budget for services as a real, recurring line, not a one-time setup fee.

On timeline, expect months, not weeks. Across 119 reviewers on G2, the average Kyriba implementation runs about eight months, and large global rollouts can run longer. Bank connectivity is usually the bottleneck: a bank outside the prebuilt library can take considerably longer to connect and test.

What drives the total cost of ownership

The headline subscription understates the real number. A few line items commonly push total cost of ownership higher, per third-party trackers like Vendr:

• Bank and SWIFT connectivity: SWIFT connectivity is estimated at roughly $10,000 to $30,000+ per year, with bank-specific connectors billed separately.
• ERP integration: a one-time estimate of roughly $20,000 to $100,000+ depending on your stack.
• Data migration: roughly $10,000 to $50,000+ to move historical data in.
• Modules and add-ons: the Payments module alone is estimated to add $50,000 to $100,000 per year on top of the base.
• Support and maintenance: commonly estimated at 15 to 20% of license value annually.

Add these up and year one can land well above the subscription figure. This is why Kyriba carries the highest perceived-cost rating on G2 and why pricing opacity is one of the most common complaints in its reviews. For a broader look at TMS budgeting, see our guide on treasury management system cost.

Is Kyriba worth the price?

For a large, multi-entity multinational running thousands of bank accounts, Kyriba often is worth it. You are paying for deep bank connectivity, payments, and risk infrastructure that would be enormously expensive to build or stitch together yourself, and at that scale the subscription is a rounding error against the treasury it manages.

For a leaner or mid-market team, the math is harder. Reviewers are candid that for simpler treasury organizations the cost can be tough to justify against the learning curve and implementation time. If you are looking at Kyriba pricing and wincing, the real question is usually not "how do I get a discount" but "am I buying more platform than my process needs." We compared the field in our guide to Kyriba alternatives.

A lower-cost path: AI agents instead of a heavy TMS

The newer option is to skip the heavy enterprise TMS for the analytical and operational treasury work and use AI agents instead. This is the category Concourse is built for. Rather than a per-module, per-entity subscription plus a months-long implementation, Concourse connects to your existing ERP, data warehouse, and banking data and runs cash forecasting, variance analysis, reconciliation, and reporting end to end, with every number traceable back to source.

The pricing model is different too: scoped to your workflows rather than assembled from modules and bank connections, and each customer is paired with a team of ex-CFOs and forward-deployed engineers who handle the integration, so professional-services hours do not become an open-ended line. For most teams it is faster and lighter to stand up than a full TMS. We put the two side by side in Concourse vs. Kyriba.

Frequently asked questions

Does Kyriba publish its pricing?

No. Kyriba does not publish a public price list or offer a self-serve tier. All pricing is quote-based and requires a sales conversation. The figures in this guide come from third-party trackers such as SpendHound, Vendr, and itqlick, not from Kyriba.

How much does Kyriba cost per year?

Based on real contracts, SpendHound reports roughly $62,000 per year on average for smaller and mid-market customers and roughly $337,000 per year for enterprises, while Vendr puts the median annual deal near $75,000. Your quote depends heavily on entities, bank connections, and modules.

How much is Kyriba implementation?

itqlick estimates Kyriba implementation and professional services at $50,000 to $150,000 for a typical deployment, rising to $200,000 to $500,000+ for large, multi-entity rollouts. Implementations average around eight months per G2 reviewers.

Is there a cheaper alternative to Kyriba?

Yes. Modern mid-market TMS options and AI-agent platforms like Concourse are generally lighter and faster to deploy. Concourse runs treasury workflows on top of your existing systems with scoped pricing rather than a per-module, per-bank enterprise subscription. See Kyriba alternatives for the full field.

The bottom line

Kyriba pricing is opaque by design, but the shape is clear enough: plan for a subscription that runs from the mid five figures for a smaller team into the mid six figures and beyond for a global enterprise, plus $50,000 to $150,000 or more for implementation, plus connectivity, integration, and services on top. For the right enterprise, that buys infrastructure worth having.

If the number is bigger than your process warrants, the better move is not to negotiate a heavy TMS down but to ask whether you need one at all. If you want to see what AI agents can do across forecasting, reconciliation, and reporting at a fraction of the setup, talk to our team and put an agent on your next forecast.