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.

20 articles · ~107 min, in 3 sections — each in reading order

TMS Fundamentals

6 articles · ~34 min
Note5 min

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.

NoteKey article8 min

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.

TMS Selection

9 articles · ~45 min
Note6 min

TMS Pricing and Licensing Models

How treasury management system vendors price and licence their software — SaaS vs perpetual, the dimensions they charge on, and what really drives the cost.

Note4 min

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.

Note5 min

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.

Note6 min

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.

Note6 min

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.

Note4 min

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

5 articles · ~28 min
NoteKey article6 min

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.

Note6 min

TMS Implementation Timeline and Phases

The phases of a TMS implementation in order, and what actually drives how long it takes — banks, entities, modules, data quality and decision speed.

Note6 min

TMS Data Migration

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.

Note4 min

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?

It's 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. An ERP (like SAP or Oracle) is the accounting and operational backbone — it owns the general ledger, AP and AR — and some companies run treasury inside it if their needs are simpler. A TMS specializes in the treasury layer on top: bank connectivity, cash positioning and forecasting, payments, and financial-risk management. Many companies run both and integrate them.

Full article →

What is the hardest part of a TMS implementation?

Bank connectivity, consistently. The software can be configured in weeks, but onboarding every bank, agreeing message formats, and testing statements and payments end to end takes far longer and depends on third parties you don't control. Connectivity, not configuration, is almost always the critical path — so it should start first.

Full article →

Follow the build → — one practical finance-systems pattern, product decision or build lesson every two weeks.