At what point does a company need a treasury management system?

When the complexity of your cash — number of banks, entities, currencies and payment volume — plus the cost of a visibility or control failure, outweighs the cost of the system and its implementation. It's rarely triggered by revenue alone. A single entity with two banks and predictable cash usually doesn't need one; a group with a dozen banks across several currencies almost always does.

Can you manage treasury without a TMS?

Yes — many companies run treasury well on spreadsheets, bank portals and their ERP, especially with low complexity. The question isn't whether it's possible but whether it's safe and efficient at your scale. Spreadsheets stop being fine when no one can answer 'how much cash do we have right now?' quickly, or when you can't prove who approved a payment.

Is a TMS worth it for a mid-sized company?

Often yes, but the case rests on complexity and risk, not size. A mid-sized company with many bank relationships, cross-border flows and manual payment approvals gets more value than a larger but simpler one. Score your banks, entities/currencies, volume/risk and control needs before deciding.

When Does a Company Need a Treasury Management System?

A company needs a treasury management system when the cost and risk of managing cash across multiple banks, entities and currencies in spreadsheets outweighs the cost of the system itself. That tipping point is driven by complexity and control — how many banks and currencies you touch, and how expensive a cash-visibility or payment-control failure would be — far more than by revenue or headcount.

So the useful question isn't "are we big enough?" It's "has our cash become complex enough, and risky enough, that spreadsheets are now a liability?" This guide gives you a straight way to answer that, including a readiness scorecard you can run in ten minutes.

It's not about company size

The instinct is to benchmark against revenue: "companies over €X buy a TMS." That's misleading. I've seen a fast-growing group with modest revenue but fifteen bank relationships across eight currencies that desperately needed a system — and a much larger, single-market business running comfortably on spreadsheets because its cash was simple and predictable.

Revenue tells you how much cash you have. Complexity tells you how hard it is to see and control — and that's what a TMS actually buys.

The four dimensions that drive the decision

Whether you need a TMS comes down to four things. Score yourself honestly on each.

Bank landscape. How many banks and accounts do you operate? Each one is a portal to log into, a statement format to reconcile, a set of signatories to manage. Two banks is a spreadsheet; a dozen is a full-time job.
Entities and currencies. Multiple legal entities and currencies multiply the reconciliation, the intercompany flows, and the FX exposure you have to see and manage.
Transaction volume and risk. High payment volumes, material FX or interest-rate exposure, and debt/investment portfolios all raise the cost of doing this by hand — and the cost of getting it wrong.
Control and audit needs. If you must prove who approved each payment and where every number came from — for auditors, for SOX, for the board — spreadsheets and email are a standing finding waiting to happen.

A treasury readiness scorecard

Score each dimension 0–3, add them up, and read off the recommendation. It's rough on purpose — the point is a shared, honest conversation, not false precision.

Dimension	0	1	2	3
Banks / accounts	1 bank	2–3	4–8	9+
Entities & currencies	1 entity, 1 currency	Few entities, 1–2 currencies	Several entities, multi-currency	Many entities, many currencies
Volume & risk	Low, no hedging	Some volume, minor FX	High volume or material FX	High volume and material risk
Control & audit	Informal is fine	Some scrutiny	Audited, SOX-lite	Strict SOX / regulated

How to read your total:

0–3 — Stay on spreadsheets (for now). Your cash is simple. A TMS would be expensive over-engineering. Invest instead in a clean process and good bank-portal discipline.
4–7 — Watch the trend. You're in the grey zone. If any dimension is trending up (new entities, new banks, a pending acquisition), start building the case and the requirements now, before the pain forces a rushed decision.
8–12 — The case is already there. The question is no longer whether but which system and how to implement it without losing control.

Signs you're past the tipping point

Beyond the score, a few lived symptoms almost always mean the moment has arrived:

You can't answer "how much cash do we have, group-wide, right now?" without a morning of chasing.
A wrong month-end number traced back to a broken spreadsheet link no one caught.
A payment was approved over email and you couldn't cleanly prove who approved it.
An FX exposure lived in one analyst's workbook, and a hedging decision depended on that file being right.
You've grown — entities, currencies, acquisitions — faster than your tooling.

Signs you're not ready yet

Buying too early is a real failure mode. Hold off if:

Your cash is genuinely simple and one person can see it all reliably.
Your process is still undefined — you don't yet know what "good" looks like. A TMS will only automate the confusion.
You'd be buying features you'll never open because a vendor demo was impressive.

In that case, spend on clarity first: define your daily cash process, clean your bank master data, and write down the two or three questions you can't answer today. That work is never wasted — and it becomes your requirements when the time does come.

The two ways this goes wrong

Buying too early — a system bought to look mature, then barely used, because the process wasn't ready and no one owned the outcome. Expensive shelfware.
Buying too late — waiting until a visibility failure or an audit finding forces a rushed selection, which produces a rushed implementation, which produces exactly the mess you feared.

The sweet spot is to decide before the crisis, with your requirements already written from the questions you can't answer today.

If you're on the fence

Do three things this quarter: run the scorecard with finance leadership, write down the questions you can't answer and the decisions they block, and look at where each dimension is trending. If the score is 8+ or climbing fast, move to selection. If it's a stable 4–7, keep the spreadsheets — but keep the requirements warm.

Part of the Treasury Management Systems guide. Start with what a TMS actually is. The newsletter sends one practical finance-systems pattern every two weeks.