Adviser Hub CloudEnterprise Wealth Tech
Pricing & Licensing

How Much Does a Treasury Management System Cost? A Five-Year Worked Example

The subscription quote is roughly a third of the bill. We model a hypothetical group with 120 bank accounts in 15 countries to show where the rest of a $2.6 million, five-year TMS budget goes, and where you can push back.

By the Adviser Hub Cloud editorial team · November 2026 · 9 min read

Why the subscription quote covers only about a third of treasury management system cost

Put two TMS proposals side by side and the headline number is the annual subscription. It's the easiest figure to compare, and on its own it's the least useful. In the five-year model below, the subscription makes up about 36% of total treasury management system cost. Bank connectivity, implementation and your own staff's time account for the rest, and those lines vary far more between vendors than the license does.

Take a hypothetical buyer. Meridian Group (a fictional example) is a regional payments and lending group with 22 legal entities and 120 bank accounts at 18 banks in 15 countries across Europe, the Gulf, India, Southeast Asia and Latin America. It wants daily cash visibility, a 13-week cash forecast, a central payment hub for supplier and intercompany payments, and basic FX exposure reporting. Hedge accounting and an in-house bank wait for a later phase.

Advertisement

Working assumptions:

  • A cloud TMS on a mid-market or upper-mid-market tier, with 25 named users
  • About 6,000 outbound payments a month and integration with one ERP
  • A phased go-live over roughly nine months
  • All figures in USD as typical 2026 market ranges. They vary by contract, region and bank relationship, so confirm with vendors and banks before you budget.

What drives the subscription line: modules, accounts and escalators

Vendors price subscriptions on some mix of modules, entities, bank accounts, named users, transaction volume (mostly payments) and hosting options. Modules and account count usually move the price most. Users matter less, though some vendors charge separately for approver-only or read-only seats.

ScopeTypical profileIndicative annual subscription (2026)
Cash visibility and basic forecastingUnder 30 accounts, a handful of entities$25,000 to $70,000
Cash, forecasting, payments and basic FX50 to 250 accounts, 10 to 40 entities$120,000 to $300,000
Full suite: risk, hedge accounting, in-house bank, netting250+ accounts, multinational group$300,000 to $1 million+

Meridian sits in the middle tier. The model assumes a quote of $180,000 a year, flat for years one and two, then a 4% annual escalator. That's a plausible figure for cloud suites such as Kyriba, GTreasury, Coupa Treasury, Nomentia or some of ION's treasury products at this scope, but actual quotes spread widely. Installed or enterprise platforms such as SAP Treasury or FIS can land higher once hosting and support are counted, and vendors that sell through regional partners often price differently from list.

Red flags to look for in the order form:

  • Uncapped or high escalators. Under Meridian's terms, a 7% to 10% uplift instead of 4% adds roughly $35,000 to $70,000 over five years, and the gap compounds every year after. Ask for a fixed rate or a cap tied to an inflation index.
  • Per-payment pricing on the payments module. It looks cheap at go-live and grows as you route more volume through the hub, which is the reason you bought it.
  • Account-band cliffs. If the price jumps sharply at 151 accounts, find out now. Acquisitions add accounts fast.
  • Billing from signature. Many SaaS contracts bill from day one, so you pay for months before anything is live. Negotiate a ramp, or a delayed start for later-phase modules.
  • Data-residency surcharges. Rules in markets such as India, Saudi Arabia, Indonesia and the EU can affect where certain payment or personal data is stored or processed. If you need a specific hosting region, get it priced in writing and have counsel confirm what the rules actually require for your business.

Bank connectivity costs by channel: SWIFT, host-to-host and APIs

Connectivity is where TMS budgets most often break. Two parties bill for it: the TMS vendor or a service bureau for the channel, and each bank for statements, messaging and payment processing. Bank charges show up on your bank fee statements, not the TMS invoice, which is why business cases miss them.

Meridian's 18 banks don't all support the same channel, which is normal across 15 countries. The model splits them like this:

ChannelBanks / accountsOne-time setupAnnual run cost
SWIFT (via vendor service bureau or Alliance Lite2-style access)8 banks / 78 accountsAbout $9,000 per bank: $72,000$35,000 channel fee + ~$37,000 bank statement and messaging charges: $72,000
Host-to-host (direct file transfer)3 banks / 22 accountsAbout $25,000 per bank: $75,000About $8,000 per bank: $24,000
Bank APIs4 banks / 12 accountsAbout $10,000 per bank: $40,000About $4,000 per bank: $16,000
Manual file import / portal download3 banks / 8 accountsMinimalAbsorbed in staff time
Total18 banks / 120 accounts$187,000$112,000

SWIFT

SWIFT is the default for large international banks, and it scales: one connection reaches many banks. The fixed channel fee carries most of the cost, so each additional bank mainly adds onboarding work (mandates, key exchange, format testing) plus that bank's own charges. Per-account statement fees typically run in the tens of dollars a month; the model uses about $40, but schedules differ widely by bank and country. Plan to work in ISO 20022 formats such as camt.053 for statements and pain.001 for payments, as banks keep moving corporate channels off legacy MT messages.

Host-to-host

Large domestic banks in markets such as India, Brazil, Mexico and parts of Southeast Asia often prefer host-to-host links with local file formats. It's the most expensive channel per bank to set up, because each connection is a small integration project, and certificate renewals and format changes add ongoing cost.

APIs

APIs are the cheapest to set up and the closest you'll get to real-time balances. Coverage is uneven, though. Corporate APIs tend to be most mature at banks in the UK, the EU, Singapore and the US; many banks elsewhere offer balance reporting by API but not payment initiation. Some also charge for higher API tiers.

For a footprint like Meridian's, a SWIFT backbone with targeted host-to-host and API links is the right mix. Going API-only across 15 countries would leave gaps that get filled with manual work.

Implementation fees and the internal effort nobody invoices

The model assumes $320,000 in vendor or partner professional services: $260,000 in year one for cash visibility, forecasting and the first payment flows, and $60,000 in year two for the remaining payment types and FX reporting. At this scope, $250,000 to $450,000 is a realistic range. Fixed-fee bids sit toward the top; time-and-materials bids look cheaper but carry the overrun risk.

Add a 15% contingency ($76,000) on implementation and connectivity setup. Bank onboarding nearly always runs long, because KYC paperwork, signatory mandates and test cycles move on the bank's timeline, not yours.

What usually pushes implementation over budget:

  • ERP integration for payment files and accounting postings, especially with heavily customized ERPs
  • Payment approval workflows that differ by entity or country
  • Forecast data feeds from business units that have never produced one
  • Information security and vendor-risk reviews, which regulated institutions should expect to take weeks
  • Format testing for every bank and payment type

Internal effort

Your own people are the line most often missing from the business case. The model assumes, over the nine-month project:

  • A treasury lead at 50%
  • Two treasury analysts at 30% each
  • An IT integration engineer full time for six months
  • A project manager at 50%

That's about 1.7 FTE-years. At an assumed loaded cost of $140,000 per FTE-year, it comes to $240,000 in year one, plus $40,000 for phase two. Loaded costs vary sharply by location: a team in Bengaluru, Manila or Bogotá costs a fraction of one in London, Zurich or New York, so use your own rates.

After go-live, budget roughly half an FTE for administration, bank changes, user access and format maintenance: $70,000 a year in the model, half that in year one.

The five-year total, and where to push back in negotiation

Here is Meridian's five-year picture in thousands of USD. The company is hypothetical; the cost lines are ones real buyers pay.

Cost line ($000)Year 1Year 2Year 3Year 4Year 5Total
SaaS subscription180180187195202944
Connectivity setup1870000187
Connectivity run costs56112112112112504
Implementation services26060000320
Contingency (15%)76000076
Internal project effort24040000280
Ongoing internal admin3570707070315
Total1,0344623693773842,626

Year-one connectivity run costs are halved because banks go live in waves. Over five years the split is roughly:

  • Subscription: 36%
  • Connectivity: 26%
  • Your own people: 23%
  • Implementation and contingency: 15%

That's about $4,400 per bank account per year, a handy sanity check on whether a proposal fits your footprint. Treat it as a figure from this model, not a market benchmark: a smaller account base or cheaper local staff will move it a lot.

Where the negotiation leverage is

  • Ramp the subscription. Paying 50% until go-live would save Meridian roughly $60,000 to $90,000, depending on how long go-live takes. That's often easier to win than an equivalent headline discount.
  • Bundle connectivity. Ask the vendor to fold service bureau fees and a set number of bank onboardings into the subscription, with a fixed price for each additional bank.
  • Re-paper bank fees. Statement and messaging charges are negotiable with relationship banks, especially if you consolidate volume onto fewer of them.
  • Close accounts first. Every dormant account you shut before implementation removes onboarding work, bank fees and possibly an account-band step-up.

The decision rule: if two vendors' five-year totals are within 10% of each other, choose on bank coverage in your hardest markets, not on subscription price. Connectivity gaps become manual work that never appears in a proposal. Next step: send every shortlisted vendor this seven-line template, have them price it against your actual bank list, and add your banks' fee schedules yourself.

Frequently asked questions

What is a realistic budget for a mid-sized treasury management system?

For a group with 50 to 250 bank accounts that needs cash visibility, forecasting and payments, subscriptions typically run $120,000 to $300,000 a year in 2026 market terms. Five-year total cost, including connectivity, implementation and internal staff, often comes to two to three times the subscription total; in our hypothetical model it's about 2.8 times. Pricing varies by contract and region, so confirm figures with vendors.

Is SWIFT connectivity always necessary for a TMS?

No. If most of your accounts sit with a few banks offering strong APIs or host-to-host links, you may not need it. As the number of banks and countries grows, one SWIFT connection usually becomes cheaper to run than many separate direct links, though the tipping point depends on your banks and fee schedules. Most multinational groups end up with a mix of channels.

How long does a TMS implementation usually take?

A phased rollout of cash visibility, forecasting and payments across around 100 accounts typically takes six to twelve months. Bank onboarding is usually the bottleneck, because KYC, mandates and format testing run on each bank's schedule. Adding hedge accounting or an in-house bank can extend the timeline by several months.

Who pays the bank fees for statements and payment messages?

You do. Banks bill you directly, separately from the TMS vendor, which is why these fees are easy to leave out of the business case. Charges vary widely by bank and country, so pull your current fee schedules and negotiate them alongside the TMS contract.

Written by the Adviser Hub Cloud editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.