Treasury & Liquidity Management Solutions

Key Takeaways

›Bank connectivity is the schedule risk, not the software. Establishing connections to your specific banking partners is the most common source of delay — ask every vendor how many of your banks they already connect to in production.
›Kyriba and FIS Quantum lead the field; SAP Treasury and Risk Management is the natural default where the ERP is already SAP and treasury data should not leave it.
›ION Treasury suits treasuries with heavy risk and derivatives requirements; TIS and Coupa Treasury are narrower, payment-hub-first choices rather than full treasury platforms.
›A TMS is never a standalone implementation. ERP, banking partners and risk systems dominate the integration effort, and pricing the project on license cost alone will understate it badly.
›Cross-border payments are now ISO 20022-only: Swift ended MT coexistence on 22 November 2025 and Fedwire migrated on 14 July 2025, so payment-hub readiness is a present-tense requirement.

At a Glance

Treasury & Liquidity Management Solutions: Vendors Compared

8 platforms, assessed against the criteria in this guide. The positions are our opinion — here is how we evaluate.

Vendor names link to the full profile further down the page; where we also list the vendor, “Directory” opens its entry.
Vendor	Position	Best for
Kyriba Directory profile ›	Leader	Mid-to-large enterprises that want a cloud TMS with forecasting and a payment hub
FIS Quantum	Leader	Large multinationals with complex multi-entity, multi-currency treasury operations
ION Treasury Directory profile ›	Strong Contender	Commodity-exposed corporates in energy, mining and agriculture
SAP Treasury and Risk Management	Strong Contender	SAP S/4HANA organizations with relatively simple treasury needs
TIS (Treasury Intelligence Solutions)Directory profile ›	Emerging	Organizations that want a bank connectivity and payments layer without replacing their TMS
Coupa Treasury Directory profile ›	Emerging	Coupa customers that want treasury inside their spend management platform
HighRadius Directory profile ›	—	Mid-market and enterprise finance teams whose first need is cash visibility and forecasting
Nomentia Directory profile ›	—	European mid-market and upper mid-market treasury teams with many banks and entities

Section 1

Executive Summary

In an era of volatile interest rates and persistent geopolitical risk, real-time cash visibility is not a treasury luxury — it is a CFO imperative. Firms that cannot see their global cash position in real time are making capital allocation decisions in the dark.

Treasury and liquidity management solutions provide the operational backbone for corporate treasury functions: cash position aggregation across bank accounts globally, cash flow forecasting using AI/ML models, payment processing through bank-agnostic payment hubs, FX exposure management, and investment/debt management. The modern TMS has evolved from a back-office record-keeping system into a strategic platform for working capital optimization.

This guide scores six platforms in depth: Kyriba, FIS Quantum, ION Treasury (formerly Openlink/Wallstreet Suite), SAP Treasury and Risk Management, TIS (Treasury Intelligence Solutions), and Coupa Treasury. We assess each across cash management depth, forecasting capabilities, payment hub functionality, and total cost of ownership. It also profiles two platforms built around cash visibility and forecasting that are not scored here: HighRadius and Nomentia.

22 Nov 2025Swift ended MT/ISO 20022 coexistence for cross-border paymentsSource — Swift

14 Jul 2025Fedwire Funds Service moved to the ISO 20022 message formatSource — Federal Reserve Financial Services

6Platforms scored in this guide

Section 2

Market Overview

The treasury technology market is undergoing its most significant transformation in a decade, driven by three forces: the shift to cloud-native SaaS platforms (eliminating on-premises TMS maintenance burden), the integration of AI/ML for cash forecasting (replacing manual spreadsheet-based forecasts), and the convergence of treasury with payments (payment hubs and payment factory architectures).

The competitive landscape has also shifted. Kyriba has established itself as the SaaS market leader for mid-to-large enterprises. FIS Quantum continues to dominate at the largest multinationals with complex treasury operations. ION Treasury (which consolidated Openlink, Wallstreet Suite, and IT2) serves the most complex treasury and commodity trading operations. Meanwhile, SAP Treasury remains the default choice for SAP-centric organizations, and newer entrants like TIS and Coupa are disrupting with focused, modular approaches.

🎯

Strategic Impact

Treasury technology directly impacts three CFO priorities: (1) working capital efficiency — real-time visibility enables meaningful trapped cash release for large multinationals, (2) financial risk management — automated FX and interest rate hedging reduces earnings volatility, and (3) payment fraud prevention — centralized payment hubs with sanction screening and approval workflows materially reduce payment fraud exposure.

API-based bank connectivity is replacing file-based SWIFT and host-to-host connections, enabling real-time cash position updates rather than end-of-day batch processing. This shift is particularly important for firms operating in high-velocity cash environments such as retail, logistics, and e-commerce.

⚠️

Common Pitfall

The most expensive TMS mistake is treating it as a standalone implementation. Treasury systems must integrate with ERP (SAP, Oracle), banking partners (SWIFT, APIs), and risk systems.

Section 3

Key Capabilities & Evaluation Criteria

Capability Domain	Weight	What to Evaluate
Cash Visibility & Positioning	25%	Real-time bank balance aggregation, multi-entity cash positioning, intercompany netting, and cash pool management
Cash Forecasting	20%	AI/ML-powered forecasting, scenario analysis, forecast-vs-actual variance tracking, ERP data integration for AP/AR flows
Payment Hub	20%	Bank-agnostic payment processing, SWIFT/API connectivity, sanction screening, approval workflows, payment factory support
FX & Risk Management	15%	FX exposure management, hedge accounting (ASC 815/IFRS 9), deal capture, mark-to-market, and counterparty risk
Debt & Investment Management	10%	Debt portfolio tracking, covenant compliance monitoring, investment policy compliance, money market fund connectivity
Reporting & Compliance	10%	Board-level treasury dashboards, regulatory reporting, audit trails, SOX compliance support, multi-GAAP accounting

💡

Evaluation Tip

During the vendor demo, request a live walkthrough of bank connectivity setup for your specific banking partners. The time and cost to establish bank connections is often the #1 implementation delay. Ask how many of your banks have pre-built API connectors vs. requiring custom SWIFT configuration.

Section 4

Vendor Landscape & Profiles

Kyriba

Leader

Strengths: Choose it when cash visibility and payments are the core need. It is a cloud TMS with machine-learning cash forecasting, a large library of pre-configured bank connections, a payment hub with fraud detection and sanctions screening, and an API marketplace.

Considerations: FX and derivatives management is less deep than specialist platforms for complex treasury operations.

FIS Quantum

Leader

Strengths: Choose it when entity count, FX and derivatives complexity drive the decision. It covers exotic instruments, debt management with covenant tracking, regulatory reporting and SWIFT connectivity.

Considerations: It has on-premises heritage, with Quantum Cloud as the cloud path. Implementations are long and need dedicated Quantum expertise on staff or through partners.

ION Treasury

Strong Contender

Strengths: Pick it when commodity hedging sits beside treasury. Its Openlink heritage brings derivatives and commodity risk management with ETRM integration, and it is offered in cloud and on-premises.

Considerations: ION's portfolio spans several acquired platforms, including Openlink, Wallstreet Suite and IT2, so product breadth adds implementation complexity and buyers should confirm the roadmap for the one they pick.

SAP Treasury and Risk Management

Strong Contender

Strengths: Choose it when SAP is the primary ERP and treasury should run on the same data. Cash positions come straight from SAP transactions, and hedge accounting and debt management integrate with SAP accounting.

Considerations: Functional depth, bank connectivity and payment hub capabilities are lighter than dedicated TMS platforms, and it is only viable where SAP is the primary ERP.

TIS (Treasury Intelligence Solutions)

Emerging

Strengths: Pick it when payments and bank connectivity are the gap. It is a cloud platform with pre-built bank connections and payment tracking that layers on top of an existing ERP or TMS, with modular pricing.

Considerations: It is not a full TMS: FX and derivatives management is limited and debt and investment management are absent.

Coupa Treasury

Emerging

Strengths: Choose it when procure-to-pay data should feed treasury. Built on the Bellin TMS that Coupa acquired, it forecasts cash from AP and AR data and ties working capital analytics to procurement.

Considerations: Its value is greatest alongside the wider Coupa platform. FX and debt management are basic, and the bank connectivity library is smaller than specialist providers'.

HighRadius

Profiled, not scored

Strengths: Look at it when forecasting is the problem to solve. HighRadius Treasury gives a real-time view of cash across bank accounts and machine-learning cash forecasts, and connects to a large library of ERPs and banks; it is often added by firms already using HighRadius for receivables or the financial close.

Considerations: It is oriented to cash and forecasting rather than full front-to-back treasury, so deal and hedge accounting are not its core. Not scored in this guide. Ask for a forecast built from your own bank and ERP data, as for the others.

Nomentia

Profiled, not scored

Strengths: Consider it for multi-bank, multi-entity control in Europe. Nomentia is a modular cloud treasury and cash management suite covering cash visibility, forecasting, payments and managed bank connectivity, with an in-house bank for intercompany netting and pooling.

Considerations: Its bank network is strongest in Europe and thinner in North America. Not scored in this guide. Ask for a forecast built from your own bank and ERP data, as for the others.

Section 5

Vendor Scoring & Rankings

Scores are on a 1–5 scale (5 = best-in-class) across weighted evaluation criteria. HighRadius and Nomentia are profiled above but not scored.

Vendor	Cash	Forecast	Payments	FX/Risk	Debt	Report	Weighted
Kyriba	5	5	4	4	4	4	4.5
FIS Quantum	5	3	5	5	5	4	4.5
ION Treasury	4	3	4	5	4	3	3.9
SAP Treasury	3	2	3	3	3	4	2.9
TIS	4	3	5	2	1	3	3.3
Coupa Treasury	3	4	3	2	2	3	2.9

Section 6

Implementation Timeline

TMS implementations are heavily dependent on bank connectivity setup and ERP integration. Plan for a phased rollout by region and function.

Phase 1

Discovery & Design (Months 1–3)

Map all bank accounts, entities, and cash flow structures. Document current-state treasury processes and pain points. Define target-state operating model. Prioritize bank connectivity requirements. Design ERP integration architecture.

Phase 2

Core Configuration & Bank Connectivity (Months 4–7)

Configure organizational structure, account hierarchies, and user roles. Establish bank connections (SWIFT, host-to-host, API). Build cash positioning and forecasting models. Configure payment workflows and approval matrices. Integrate with ERP for AP/AR data feeds.

Phase 3

Testing & Regional Rollout (Months 8–11)

Conduct parallel operations with legacy processes. Test payment processing end-to-end with each banking partner. Roll out by region starting with highest-value treasury centers. Train treasury staff on new workflows and analytics. Validate cash forecasting accuracy against actuals.

Phase 4

Optimization & Advanced Features (Months 12–16)

Activate AI-powered forecasting with sufficient historical data. Implement FX management and hedge accounting modules. Enable intercompany netting and cash pool optimization. Deploy board-level treasury dashboards. Establish ongoing vendor governance and SLA monitoring.

Section 8

Peer Perspectives

“Moving from spreadsheets to a treasury management system can unlock trapped cash and provide real-time visibility across a large, global set of bank accounts — shifting the CFO from a weekly cash email to a daily dashboard.”

— Practitioner perspective

“Bank connectivity is often the bottleneck. Connecting a large number of banking relationships can take far longer than estimated, so it is worth starting the connectivity workstream well before the rest of the platform implementation.”

— Common implementation lesson

“For organizations already migrating to a major ERP, the integration cost of a separate TMS can outweigh its functional advantages. A native treasury module may not be best-in-class, but direct data flow from the ERP can meaningfully reduce operational complexity.”

— Practitioner perspective

Section 9

Red Flags & Pitfalls to Avoid

Treasury technology purchases often look straightforward in demos but reveal painful gaps during implementation. These red flags will help you avoid the most costly mistakes.

⚠️

Red Flags to Watch

Bank connectivity quoted as “included” without specifying your banks. Pre-built connectors vary enormously by vendor. Real-world accuracy degrades significantly from demo conditions.
No support for in-house banking or intercompany netting. If your treasury strategy involves centralizing liquidity across entities, a TMS without IHB and netting capabilities will force you into manual workarounds that defeat the purpose of automation.
Payment approval workflows that cannot mirror your SOX control matrix. If the platform cannot replicate your existing segregation-of-duties requirements, your internal audit team will block go-live.
FX management limited to spot trades with no hedge accounting support. Corporates managing FX risk need ASC 815/IFRS 9 compliant hedge designation, effectiveness testing, and journal generation. A platform that only captures trades without accounting integration creates more work than it eliminates.
No real-time bank balance APIs — only end-of-day MT940 statements. In 2026, real-time cash visibility requires API-based bank connectivity. A platform relying solely on file-based statement processing delivers yesterday’s cash position, not today’s.
Multi-entity support that requires separate instances per legal entity. True multi-entity architecture should provide consolidated and entity-level views from a single platform instance, not siloed deployments stitched together with reports.

Section 10

Key Questions to Ask Vendors

Use these questions during demos and vendor due diligence to separate genuinely capable platforms from those that demo well but disappoint in production.

💡

Cash Visibility & Forecasting

How many of our specific banking partners have pre-built API connectors, and what is the average time to establish a new bank connection for banks not in your library?
Can you demonstrate your AI forecasting accuracy metrics from an existing client with a similar entity structure and industry to ours?
How does your platform handle cash visibility for countries with capital controls or restricted currency accounts (e.g., China, India, Brazil)?

💡

Payments & Risk

Walk us through a cross-border payment from initiation to bank confirmation, including sanction screening, approval routing, and status tracking.
How do you handle payment format conversion across different banking standards (SWIFT MT, ISO 20022, local clearing formats)?
Can your FX module capture an NDF, designate it as a cash flow hedge under IFRS 9, and automatically generate the hedge accounting journal entries?

💡

Integration & Operations

What is your ERP integration architecture for SAP S/4HANA — do you use standard IDocs, APIs, or middleware, and what is the typical latency for AP/AR data?
How do you handle disaster recovery and business continuity for payment processing?

Section 11

Recommended Next Steps

Treasury technology selection requires cross-functional alignment between treasury, IT, finance, and internal audit. Follow this roadmap to build consensus and make a confident decision.

Step 1

Map Your Treasury Operating Model (Week 1–3)

Document all bank accounts, entities, cash flow patterns, and current-state processes. Quantify the cost of your current approach (trapped cash, manual FTE effort, FX losses from delayed hedging). This builds the business case that secures CFO sponsorship.

Step 2

Prioritize Requirements by Business Impact (Week 3–4)

Rank requirements using the weighted criteria in this guide. Distinguish between must-have capabilities for Phase 1 (cash visibility, payments) and Phase 2 features (AI forecasting, FX management). This prevents scope creep during vendor selection.

Step 3

Issue RFP and Conduct Demos (Week 5–10)

Shortlist a small number of vendors and require scripted demos against your specific use cases. Include a bank connectivity proof-of-concept with at least two of your primary banking partners. Insist on seeing real-time cash positioning, not pre-loaded demo data.

Step 4

Validate TCO Including Bank Connectivity (Week 10–12)

Request itemized pricing for bank connectivity setup (per-bank costs), SWIFT fees, ERP integration, and ongoing transaction-based pricing. TMS total cost of ownership is notoriously understated in initial proposals.

Step 5

Plan a Phased Implementation (Week 12–14)

Design a phased rollout starting with your highest-value treasury center and most important banking relationships, then roll out region by region. Secure executive sponsorship for the multi-phase program.

For vendor shortlisting, TCO modeling, and implementation planning tailored to your treasury operating model, explore Finantrix Buyer Guides or contact us for a dedicated treasury technology advisory engagement.

◆ Spotlight

This position is available to vendors in this category for $499 a year. Labeled as paid. It does not affect this guide's evaluation. Sponsor this guide

Frequently Asked Questions

What is the Treasury & Liquidity Management Solutions market landscape?

The Treasury & Liquidity Management Solutions market includes 8 major vendors evaluated in this guide. Evaluate treasury management systems for cash visibility, forecasting, bank connectivity, and liquidity optimization across multi-entity organizations.

How do you evaluate Treasury & Liquidity Management Solutions vendors?

Finantrix uses a weighted evaluation framework covering key capabilities, vendor landscape analysis, pricing models, implementation timelines, and peer perspectives. This 16-minute guide includes RFP templates and selection checklists for enterprise procurement.

Methodology

How We Evaluate

Weighted evaluation criteria

Cash Visibility & Positioning

Cash Forecasting

Payment Hub

FX & Risk Management

Debt & Investment Management

Reporting & Compliance

Bars are scaled to the heaviest criterion. The percentages are the real weights and add up to 100%.

We write these guides for people running a software selection. This one covers 8 platforms and should save you weeks of research, but it will not replace your own reference calls and a proof of concept.

We review vendors' websites, product documentation and press releases, along with regulatory texts and other publicly available information. Our assessments are our opinion. No vendor supplied them and nobody audited them. Use them to build a shortlist, then go and test it yourself.

The criteria weights are ours as well. We chose them for this category and publish them so you can see what we valued, and weight things differently if your situation calls for it.

No vendor pays to appear in this guide or to be described the way it is. Spotlight placements alongside our guides are paid and labeled as paid placements, and they change nothing about the evaluation.

Last reviewed November 2026. Enterprise software moves quickly and pricing is negotiated rather than listed, so parts of this will age. If we have something wrong, tell us and we will fix it. That goes double if you work for a vendor we cover.