Topic
Treasury Management Systems: Selection & Implementation
Everything here is about choosing and implementing the system corporate treasury runs on — from deciding whether you need a treasury management system at all, through the business case, selection and RFP, to implementation, testing and go-live.
For how the ERP, TMS, banks and market data connect once you've chosen, see the separate Treasury Systems Architecture guide. It's written from 18 years inside SAP FI/TRM and real treasury-transformation delivery: not vendor marketing, but what actually works, what usually goes wrong, and what I'd decide. Start with what a TMS is, then follow the path that matches where you are.
19 articles · ~117 min, in 3 sections — each in reading order
TMS Fundamentals
6 articles · ~43 minWhat treasury does and what a TMS is, how to choose one, whether you need one at all (vs ERP or spreadsheets), modular vs monolithic, requirements checklist.
What Does a Corporate Treasury Do?
Corporate treasury manages a company's money — cash, liquidity, funding and risk. What treasury actually does, and how it differs from accounting.
What Is a Treasury Management System (TMS)?
A treasury management system (TMS) manages cash, liquidity, payments, risk and bank connectivity — what it does, when you need one, and how it fits.
The Best Treasury Management System: How to Choose
There is no single best TMS — the right one depends on your category. A vendor-neutral guide to the four kinds of TMS, who each fits, and how to decide.
Do You Need a TMS? TMS vs ERP vs Spreadsheets
Do you need a TMS, your ERP's treasury module or just spreadsheets? A readiness scorecard, a head-to-head comparison and the signals it's time to step up.
Modular Treasury Management System vs Monolithic Suite
A modular treasury management system is bought module by module on a shared core treasury system. Which modules separate, and when it beats a single suite.
Treasury Management System Requirements Checklist
A practical TMS requirements checklist — cash, connectivity, payments, risk, accounting, reporting, plus the non-functional requirements teams forget.
TMS Selection
9 articles · ~49 minBusiness case and TCO, build vs buy, whether a Magic Quadrant exists, demo scorecard, SaaS vs on-premise, cloud security, then the RFP and selection process.
Building the Business Case for a Treasury Management System
How to build a credible TMS business case: the quantifiable benefits, the full cost of ownership, and how to make it stand up to CFO scrutiny.
TMS Pricing, Licensing and Total Cost of Ownership
How TMS vendors price and licence their software — SaaS vs perpetual, what they charge on — and the total cost of ownership that sits behind the quote.
Build vs Buy a Treasury Management System
For almost every corporate, buying a TMS beats building one, because a package embeds decades of connectivity and compliance. When build makes sense, and why.
Is There a Gartner Magic Quadrant for TMS?
There is no dedicated Gartner Magic Quadrant for treasury management systems. What Gartner actually covers, and how to shortlist a TMS without a quadrant.
TMS Vendor Demo Questions and Evaluation Scorecard
How to evaluate TMS vendors: the questions to ask in a demo, and a weighted scorecard to compare them — driven by your requirements, not their sales script.
SaaS vs On-Premise Treasury Management System
Cloud SaaS is the default TMS deployment model; on-premise the exception for control, data-residency or integration. How they differ on cost, upgrades and exit.
TMS Cloud Security and Data Residency
A cloud TMS holds your bank details and payment capability — the security, certification and data-residency questions to ask a vendor before you sign.
How to Write a TMS RFP (Request for Proposal)
A TMS RFP is the structured document that asks shortlisted vendors to propose against your requirements — how to write one that gets comparable, useful answers.
How to Run a TMS Selection Process
A TMS selection process is the structured path from ‘we need a system’ to ‘we chose the right one’ — requirements, RFP, scripted demos, scorecard, references.
TMS Implementation
4 articles · ~25 minImplementing the chosen system: the implementation guide, migrating master data and open deals, why implementations fail, and treasury transformation overall.
Treasury Management System Implementation Guide
How a TMS implementation really runs: mobilize, design, bank connectivity, data migration, testing, cutover, hypercare. The phases, timeline and critical path.
TMS Data Migration: Moving Master Data and Open Deals
TMS data migration means moving master data, open positions and live deals into a new treasury system — cleanly, and reconciled so your positions still tie out.
Why TMS Implementations Fail (and How to De-Risk Yours)
Why TMS implementations fail: rarely the software — it's the treasury change. IT-project thinking, bank connectivity, dirty data, no one owning the outcome.
Treasury Transformation: A Practical Guide
Treasury transformation is upgrading how treasury operates, usually around a new TMS. Why it succeeds on outcomes and delivery discipline, not technology.
Free tools for this topic
Frequently asked questions
What is a treasury management system in simple terms?
A treasury management system is the software corporate treasury uses to see and control the company's cash. It pulls in bank balances and statements, forecasts cash, sends and tracks payments, manages FX, debt and investments, and keeps an auditable record of it all — the jobs a finance team used to do in a wall of spreadsheets.
Full article →What are the phases of a TMS implementation?
Typically: mobilize and scope, design (target operating model and configuration decisions), build and configure, bank connectivity, data migration, testing (system integration testing then user acceptance testing), cutover and go-live, and hypercare. Bank connectivity and data run in parallel from early on because they are the usual critical paths.
Full article →Why do treasury management system implementations fail?
Almost never because of the software. They fail because the project is run as an IT install rather than a treasury change programme; because bank connectivity — the real critical path — is underestimated; because dirty master data is migrated as-is; because forecasting expectations outrun the data; and because tasks are owned but the outcome is not. Fix those and the technology rarely gets in the way.
Full article →Do I need a TMS if I already have an ERP?
Not always. If your treasury needs are moderate, the ERP's own treasury module can be enough; a TMS earns its place when bank connectivity, forecasting and risk outgrow it, and many large companies run both.
Full article →How long does a TMS implementation take?
It depends almost entirely on scope. A focused single-entity, few-banks cash implementation is typically a matter of months; a multi-entity, multi-bank, multi-module programme runs considerably longer — often past a year. Anyone quoting one exact number without knowing your bank, entity and module count is guessing. The software configuration is rarely the long pole.
Full article →Work with me → — the workflows this hub documents are exactly the kind I redesign with AI: slow, manual, exception-heavy, and still answerable to a control review.