Four Facts That Narrow the Shortlist Before Any Demo
Most treasury teams start by comparing feature matrices. That rarely helps. Kyriba, SAP, FIS, ION, GTreasury, Coupa and Nomentia all cover cash positioning, payments, forecasting and some risk management. What separates them is how well each handles the shape of your treasury. Picking the best treasury management system mostly means ruling out the platforms built for a different shape.
Four facts decide most of the shortlist. Write them down before you take a single vendor call.
- Banks, accounts and entities. A group with 8 banks and 40 accounts has very different needs from one with 90 banks, 1,200 accounts and 150 legal entities. Bank connectivity is where projects slip and recurring costs build, so the number of banking relationships matters more than headcount or revenue.
- Currencies and countries. Ten freely convertible currencies are simple. Indian rupee, Chinese renminbi, Brazilian real, Egyptian pound or Nigerian naira bring local payment formats, central bank reporting and limits on cross-border pooling and netting. Those limits shape what an in-house bank can legally do in each country.
- ERP landscape. A single SAP S/4HANA instance points one way. Five ERPs inherited through acquisitions (say SAP ECC in Europe, Oracle in North America, NetSuite in Asia-Pacific subsidiaries and a local system in Latin America) point another. That calls for treasury software that sits above the ERPs, not inside one.
- In-house banking and payment centralization. If you plan to run payments-on-behalf-of (POBO), collections-on-behalf-of (COBO), intercompany netting or a full in-house bank within three years, choose for that now. Retrofitting is expensive.
Some groups face a fifth factor: instrument complexity. If you carry a large debt book, interest rate or cross-currency swaps or commodity hedges, and apply hedge accounting under IFRS 9 or ASC 815, the field narrows quickly. Valuation and accounting depth separates platforms more than anything else.
The rest of this guide sorts the seven platforms against these factors and names the profile each fits best.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Kyriba, SAP Treasury and FIS Quantum: The Heavyweights and Their Natural Buyers
Kyriba
Kyriba is a cloud-native SaaS platform that doesn't depend on any ERP. It has invested heavily in bank connectivity: SWIFT service bureau access, host-to-host links, EBICS for banks in markets such as Germany, France and Switzerland, and a growing set of bank APIs. Core modules cover cash management, payments, cash forecasting, FX risk, and working capital and supply chain finance.
Best fit: a multinational with 30 or more banks, several ERPs and a central treasury that wants one SaaS layer for visibility and payments in every region. It's a common default on shortlists for multinationals with mixed ERP landscapes, and for good reason.
Watch for: pricing is per module, and costs rise as you add payments, risk and connectivity bundles. Groups with complex derivatives books or heavy hedge accounting should test its instrument coverage against FIS or ION in a scripted session.
SAP Treasury and Risk Management
Inside S/4HANA, SAP offers Treasury and Risk Management, Cash Management, in-house cash and in-house banking functions, Advanced Payment Management and, through its Business Technology Platform, Multi-Bank Connectivity. Because treasury shares a ledger with accounting, postings, intercompany settlement and reconciliation need fewer interfaces.
Best fit: groups standardized (or committed to standardizing) on S/4HANA that want an in-house bank, payment factory and hedge accounting inside the ERP. For a large SAP-centric group running POBO across dozens of entities, this is usually the strongest choice.
Watch for: you need SAP treasury specialists, in-house or through an integrator, and those skills carry a premium in every market. Subsidiaries on non-SAP ERPs need integration work. Multi-Bank Connectivity is typically a separate subscription. Treasury users sometimes find the interface heavier than standalone SaaS tools, so test daily cash positioning with your own analysts.
FIS Quantum
Quantum is FIS's long-established platform for transaction-heavy treasuries. It covers debt, investments, money markets, FX and interest rate derivatives, and hedge accounting, and has been offered on-premise or hosted by FIS. FIS sells more than one treasury product, so confirm which platform and deployment model a proposal covers.
Best fit: corporates with large, active debt and investment portfolios, utilities and energy companies with complex hedging, financial-sector corporate treasuries, and public-sector bodies with heavy reporting duties. If your treasury spends more time on instruments than on cash visibility, Quantum belongs on the list.
Watch for: its cash forecasting and user experience are generally seen as less modern than cloud-native rivals. Some groups pair it with separate cash forecasting software. Count that second contract in total cost.
ION, GTreasury, Coupa Treasury and Nomentia: Narrower Fits, Often Better Ones
ION Treasury
ION isn't one product. Through acquisitions it has built a portfolio that includes Wallstreet Suite, Openlink, IT2, Reval, ITS and Treasura. These range from heavy front-to-back systems used by banks and very large corporates to lighter tools for mid-sized treasuries. The first question for ION is which product it's proposing and why.
Best fit: it depends on the product. Wallstreet Suite suits banks, large corporates and trading-room-style treasuries. Reval is a cloud option strong on FX risk and hedge accounting for mid-to-large corporates with significant exposures. Treasura and ITS target smaller teams that need cash and payments without heavy instrument coverage.
Watch for: with any vendor built through acquisition, get the roadmap for your specific product, the support model in your time zone and renewal price caps in writing. A demo of one ION product doesn't stand in for another.
GTreasury
GTreasury is a SaaS platform for mid-sized to large corporates. It's strong in cash positioning, forecasting, and debt and investment management, with risk and hedge accounting modules. Its ClearConnect gateway handles bank connectivity, including APIs and traditional file channels.
Best fit: a group with 10 to 60 banks, two to five ERPs and a lean treasury of two to six people that wants fast time to value and reasonable instrument coverage without a large integrator. Its client base leans toward North America, though it serves global groups. If most of your entities are in Asia, the Middle East or Latin America, check where implementation and support resources actually sit.
Watch for: confirm coverage of your local banks and file formats outside its strongest markets, and check how much configuration you can do yourselves without paid services.
Coupa Treasury
Coupa Treasury is the former Bellin tm5, a German-built platform known for payment factories, in-house banking, intercompany netting and bank account management. Coupa acquired it and has linked it to its spend management suite.
Best fit: European-headquartered or Europe-heavy groups centralizing payments through POBO and COBO, running an in-house bank over multiple ERPs, and groups already using Coupa for procure-to-pay that want supplier payments and treasury on one platform. If you want in-house banking without moving to S/4HANA, it's one of the strongest options.
Watch for: ask how treasury fits into the wider Coupa roadmap. Test forecasting and complex derivatives if they matter to you; its heritage is payments and liquidity more than trading.
Nomentia
Nomentia is headquartered in Finland and built around payments, bank connectivity, cash management and cash forecasting. It has added virtual account and in-house banking capabilities through acquisition. Its sweet spot is a payment hub that consolidates outgoing payments from many ERPs and gives cash visibility, without the weight of an instrument-heavy TMS.
Best fit: European mid-sized to large groups with high payment volumes, many ERPs and a priority on payment control, fraud prevention and bank consolidation. It also suits finance teams that want a payment hub first and a fuller TMS later.
Watch for: derivatives and hedge accounting depth is limited compared with FIS, ION or SAP. Its presence outside Europe is growing, so verify local bank coverage and support hours for your regions.
Fit Matrix: Which Platform Suits Which Treasury Profile
The table maps common treasury profiles to a starting shortlist. It isn't a ranking. A platform under "also consider" can still win once you run scripted demos.
| Treasury profile | Typical shape | Start shortlist with | Also consider |
|---|---|---|---|
| Lean mid-market group | 5–20 banks, 2–3 ERPs, 1–3 treasury staff | GTreasury, Nomentia | Kyriba, ION (Treasura or ITS) |
| Decentralized multinational | 30–150+ banks, 50+ entities, several ERPs | Kyriba | GTreasury, Coupa Treasury |
| SAP-standardized group | Single S/4HANA instance, in-house bank planned | SAP Treasury and Risk Management | Coupa Treasury, Kyriba as an overlay |
| Instrument-heavy treasury | Large debt book, swaps, commodity hedges, IFRS 9 or ASC 815 hedge accounting | FIS Quantum, ION (Wallstreet Suite or Reval) | SAP TRM |
| Payment factory in Europe | High volumes, POBO/COBO, netting, multiple ERPs | Coupa Treasury, Nomentia | SAP, Kyriba |
| Restricted-currency footprint | Significant operations in India, China, Brazil, Egypt or Nigeria | Whichever finalist proves your local bank formats | Validate all finalists country by country |
The last row matters more than it looks. In markets like China, India and Brazil, cross-border pooling, netting and POBO are restricted or need specific approvals and structures. Local formats, such as Brazil's CNAB files, can need dedicated mapping. No vendor deck tells you whether your banks in Chennai, Shanghai or São Paulo are already live on its platform. Ask for that list by name.
Worked example (hypothetical)
Say a manufacturer headquartered in Singapore has 60 entities, 45 banks across 22 countries and three ERPs: SAP ECC in Europe, NetSuite in Asia-Pacific subsidiaries and a local ERP in Brazil. Treasury has four people. The goals are daily global cash visibility, payment controls and a 13-week cash forecast. Hedging is limited to FX forwards.
Kyriba is the natural first pick because the group needs an ERP-independent layer across a wide bank footprint. GTreasury is a credible second, provided it shows Asia-Pacific support coverage. SAP treasury doesn't make sense until an S/4HANA migration is funded and scheduled. FIS Quantum would be overbuilt for a forwards-only hedging program.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
What a Treasury Platform Costs in 2026 and What Drives the Bill
Vendors rarely publish prices, and quotes vary widely by region, contract length and negotiating leverage. The ranges below are typical 2026 market ranges for indicative budgeting only. Confirm figures with each vendor; local pricing and currency terms differ.
| Cost element | Mid-market group | Large multinational | Notes |
|---|---|---|---|
| Annual SaaS subscription | USD 40,000–150,000 | USD 150,000–600,000+ | Driven by modules, entities, users and bank accounts |
| Implementation (one-time) | USD 40,000–200,000 | USD 250,000–1,500,000+ | Often roughly 0.5–1.5x first-year subscription for SaaS platforms |
| Bank connectivity | USD 10,000–50,000 per year | USD 50,000–250,000+ per year | SWIFT service bureau, host-to-host or API fees, plus bank-side charges |
| SAP treasury in S/4HANA | Rarely a mid-market choice | USD 500,000–3,000,000+ in integrator fees | Licensing is often bundled into the wider SAP contract |
| Internal team time | 0.5–1 FTE during the project | 2–5 FTE during the project | Treasury, IT and accounts payable time is usually underbudgeted |
Five factors move the bill most:
- Bank connections and formats. Every new bank, file type (MT940, camt.053, pain.001, local formats) and channel adds setup and recurring cost. Consolidating banks before go-live is often the biggest single saving.
- Module count. Cash visibility and payments are the base. Forecasting, FX risk, debt and investments, hedge accounting, in-house banking and netting are usually priced separately.
- Entities, accounts and users. Some vendors price by entity, others by bank account or named user. Model three-year growth, including acquisitions, against each method.
- Hosting region and data residency. Rules such as the EU's GDPR, India's Digital Personal Data Protection Act, Saudi Arabia's PDPL and China's PIPL can affect where payment and beneficiary data is stored and processed. A dedicated regional instance can cost more. Have qualified counsel confirm what applies to your entities.
- Renewal uplift. Multi-year contracts with uncapped renewals are a common source of cost surprises. Ask for a written annual cap and price protection when you add entities.
Timelines follow the same pattern. A phased SaaS rollout covering cash visibility and payments often takes 3–6 months. Adding forecasting, risk and broader bank coverage stretches it to 9–18 months. An SAP in-house bank or full payment factory across many countries can run 12–24 months.
Red Flags and a Selection Sequence That Holds Up
Failed TMS projects usually show warning signs during the sales cycle. Watch for these:
- "We connect to any bank." Ask for your banks and formats, by country, marked live in production or to be built. Anything to be built is a project risk and probably a services fee.
- Demos run only on the vendor's data. Clean sample data proves little. Insist on a scripted session using a sample of your own bank statements and payment files.
- An unnamed implementation team. Ask who will do the work, whether they're vendor staff or a partner, and where they're based. A team ten time zones from your treasury center slows every workshop.
- Vague answers on hosting. If the vendor can't say which region hosts your instance and where backups and support access sit, your data protection review will stall later.
- References that don't look like you. A single-ERP European reference tells a multi-ERP Middle East group little. Ask for references that match your bank count, region and ERP mix.
- Forecasting shown as a dashboard, not a process. Good cash forecasting software lets regional teams submit, override and comment on forecasts, and measures actual against forecast variance. A chart alone isn't forecasting.
Then run the selection in this order:
- Build your inventory. List banks, accounts, entities, ERPs, payment volumes by country and currencies with capital controls. Expect two to four weeks. It's the most valuable input to the whole process.
- Rank the four fit factors (plus instrument complexity if it applies) and agree the ranking with the CFO and IT before you contact vendors.
- Shortlist three platforms using the fit matrix. More than three dilutes your team's attention. Fewer than two removes negotiating leverage.
- Run scripted demos on your own data. Score each vendor on daily cash positioning, a cross-border payment approval, a forecast cycle and, if relevant, a hedge relationship.
- Prove connectivity with at least two of your hardest banks, ideally in a restricted-currency market, before you sign.
- Negotiate the contract with renewal caps, entity-addition pricing, service levels, data export rights at exit and a named implementation team. Have legal and data protection counsel review terms for each jurisdiction you operate in.
A decision rule: if one ERP will run most of your entities within two years, start with that ERP's treasury option and make the alternatives prove they're better. If not, pick the platform that proves live connectivity to your hardest five banks, then compare on price.