How to evaluate a treasury platform without losing a quarter

A CFO friend asked me last month to send him a comparison of treasury platforms. I had to disappoint him. The comparisons people put on the internet are bad. They are bad because they list features. Features are the wrong thing to compare.

I am going to write what I told him instead.

What does not matter

The list of features in the marketing material. They all have the same list. They all have approvals, dashboards, ERP integration, AI assistants, supplier portals, mobile apps. Every vendor in this space has the same feature page. The feature page tells you nothing about the platform.

The price per user. Treasury and AP systems are bought once every five to seven years. The five-year cost of any of them is dominated by implementation, change management, and the cost of getting the data wrong. Per-user pricing is the smallest line in your total cost.

The number of customers. Big customer lists are reassuring. They also mean the vendor's product roadmap is shaped by their biggest customers, who probably look nothing like you. A smaller vendor whose customer base is shaped like yours is usually a better bet.

What does matter

How they hold supplier identity. Ask to see the data model. Ask whether suppliers are first-class records or fields on invoices. Ask how master data deduplication works. The answer to these three questions tells you what the next four years of using that system will feel like. If they cannot answer them in a discovery call, that is itself an answer.

How bank account verification works. Ask whether the supplier-supplied bank account and the treasury-vetted bank account are the same record. If they are, you have an account substitution fraud risk built into the architecture. If they are not, ask how promotion from one to the other works and how often re-verification is required.

How approval rules are stored. Ask whether workflow steps are rows in a table or states on a record. Ask how you audit a payment two years later. If the answer involves restoring a backup or pulling logs from a third system, the platform is going to fight you every time the auditor walks in.

How the cash forecast is fed. Ask whether the forecast reads the AP system live or reads an extract. Ask how stale the data can be. Ask what happens when a payment is rescheduled at 4 pm on a Friday. The answer tells you whether the treasury and AP teams will be cooperating or fighting over the same numbers.

How the team thinks. Ask the implementation lead to walk you through their last failed implementation. If they have not had one, they are too new or too small to have built scar tissue. If they will not talk about it, they are hiding something. If they describe it candidly and tell you what they changed, you are talking to a team that has learned things you can benefit from.

What we are doing about Calabash

We will give you the data model on request. We will tell you exactly how supplier identity, bank account verification, workflow rows, and live forecast data are held. We will introduce you to our reference customer when we have one, and we will tell you we do not have one yet today. We will share what has gone wrong in the early customer conversations because the patterns are useful to the next twenty teams who ask.

If you are running a treasury evaluation right now, we are not asking for a slot in your shortlist yet. We are asking to be the second pair of eyes on the data model and architecture questions of whichever vendors are. The hour we spend on your shortlist will save you the quarter you would otherwise spend on a bad implementation. Sign up at calabash.app/b2b and we will give you the hour.