Explainer
A treasury management system gives a group one view of its cash, one route for its payments and one record of its funding and hedging. Here is when you need one, who sells them in 2026, and how to choose.
By Christopher Fagan, Managing Partner, PEF Consulting Partners
Delivered for and alongside
















A treasury management system, usually shortened to TMS, is the treasurer’s equivalent of the ERP. Where the ERP records what the business has bought and sold, the TMS records where the cash is, where it is going, and what the group has borrowed, invested and hedged.
The core capabilities fall into six areas:
None of this is exotic. Most ERPs can import a bank statement and pay a supplier. The difference is scale and control. A TMS is built to handle dozens of banks, hundreds of accounts and many currencies under one set of approvals, which is exactly where ERP cash modules start to strain.
Plenty of well run UK groups manage treasury on spreadsheets and bank portals, and for a single entity with two banks that is perfectly sensible. The question is when the risk of the spreadsheet starts to exceed the cost of a system. In my experience the signals are fairly consistent.
Two or three of those together usually justify a proper look. Payment fraud is the one I would weigh most heavily. A spoofed supplier bank detail change costs far more than a TMS licence, and central payment screening with consistent approval is one of the clearest controls a system adds.
The other trigger is change elsewhere. An ERP replacement, a refinancing or an acquisition each forces a rethink of bank connectivity, and doing it once, properly, is cheaper than patching it three times.
Bank connectivity is where treasury projects succeed or stall, and the UK rules have been moving. Swift ended its coexistence period on 22 November 2025, so ISO 20022 is now the required format for cross border payment instructions between banks, with a temporary conversion service for anything still sent in the old MT format.
Closer to home, the Bank of England has confirmed that from November 2027 purpose codes will be mandatory on all CHAPS payments sent through initiation channels within the control of CHAPS direct participants. In practice that means your bank’s portals and host to host services will need a purpose code on every high value sterling payment you send. The Bank has also said CHAPS payments will not be rejected solely for incomplete or incorrect enhanced data before the end of 2028 at the earliest, which gives some breathing room but not a reason to wait.
For a buyer, three questions follow. Can the TMS produce ISO 20022 payment files for each of your banks, with purpose codes and structured data populated from your master data rather than typed by hand? Which connectivity routes does the vendor support: direct host to host, Swift through a service bureau or Swift’s own Business Connect, or bank APIs? And who owns the bank testing, because each bank will want to certify its own formats, and that work regularly takes longer than the software configuration.
The answer to the first question often exposes gaps in supplier master data held in the ERP, which links treasury to accounts payable automation more closely than most project plans assume.
The market has consolidated and changed hands repeatedly. As of November 2026, the names a UK corporate is most likely to meet are these.
The ownership changes matter. A new owner can mean new investment or a slower roadmap, and a crypto payments company buying a TMS vendor raises fair questions about product direction that you should put to it directly.
None of the seven vendors above publishes a UK price list that I could find in November 2026. Kyriba, for example, describes its pricing as a modular subscription and asks for a call with sales. Expect every proposal to be built from the same handful of drivers:
Two costs are routinely missed. The first is bank side: setting up host to host or Swift links and testing formats with each bank takes your team’s time and sometimes carries bank charges. The second is internal ownership after go live. A TMS needs someone who maintains bank formats, user rights and market data feeds, and in a small treasury team that is a material slice of a role.
Ask for a five year cost, priced for the scope you expect in year three rather than the day one minimum. Treasury systems tend to expand once the first module proves itself.
The TMS and the ERP have to agree on cash, and the integration design decides whether they do. The usual flows are: bank statements into the TMS and then onwards to the ERP for reconciliation; approved supplier payments out of ERP payables into the TMS payment hub; forecast inputs from payables, receivables and orders; and accounting entries for deals, interest, fees and revaluations back into the general ledger.
The design decisions that cause trouble later are who owns the bank statement, where bank reconciliation is performed, and whether payments ever bypass the TMS. If the ERP and the TMS both talk to the same bank, you have two sets of controls to maintain. If month end bank reconciliation lives in a close tool such as BlackLine, decide where the statement is sourced; my BlackLine explainer covers that side.
Having delivered most of the mainstream finance platforms over 19 years, including Oracle, Dynamics, NetSuite, SAP S/4HANA, Sage, Unit4 and Access, I would add one practical point: the TMS project should share a data design with the ERP, not run alongside it. Bank account master data, entity codes, counterparties and the chart of accounts have to line up across both. Our ERP integration work starts with that mapping for exactly this reason.
Start from your treasury policy, not a feature list. Write down what you need to see, approve, hedge and report, at what frequency, and against which controls. Then score vendors on scripted demonstrations using your banks, your entities and your instruments: a real morning cash position, a payment run with your approval matrix, a forward contract from deal to accounting entry.
Bring your relationship banks in early. They will tell you which connectivity routes they support and how long format testing typically takes with them, and that should shape your timetable more than any vendor plan. Check the vendor’s security and audit reports, its data residency options, and how it supports fraud detection and sanctions screening. Ask for UK reference customers of a similar size and complexity.
Our consultants have led and analysed finance system decisions at every stage, before a migration, partway through one and after go live, and that is the perspective we bring to a treasury selection. We have no reseller or referral arrangement with any treasury vendor. Our vendor selection method applies here, and our fees are shown plainly on the pricing page.
Related reading: Kyriba explained, BlackLine explained, Accounts payable automation, Tipalti explained, FP&A software compared.
A treasury management system is software that gives a company a single view of its cash across all banks and entities, produces cash forecasts, sends and controls payments, and records foreign exchange deals, hedges, loans and investments. It connects to banks through host to host links, Swift or APIs, and to the ERP for payables, receivables and accounting entries. Larger groups use it to replace bank portals and spreadsheets.
An ERP is often enough for a single entity with a few banks and no hedging. A treasury management system becomes worthwhile when you have many banks, accounts or currencies, need a reliable daily cash position and rolling forecast, release payments from several portals, run hedging programmes, or face audit points on payment controls. Payment fraud risk is a strong reason on its own.
The vendors most UK corporates meet are Kyriba, ION Treasury with products including Wallstreet Suite and Reval, FIS with Treasury and Risk Manager Quantum Edition, GTreasury, Coupa Treasury, Nomentia and TIS. They differ in depth of risk management, payment capability, connectivity options and the size of organisation they suit, so shortlist against your own requirements rather than market rankings.
The main vendors do not publish UK list prices. Quotes are built from the modules taken, the number of entities, bank accounts and bank connections, the connectivity route such as Swift, payment volumes, users and implementation services. Bank side set up and the internal time to maintain formats and users after go live are frequently missed, so model a five year total cost.
The Bank of England has confirmed that from November 2027 purpose codes will be mandatory on all CHAPS payments sent through channels within the control of CHAPS direct participants, such as bank portals and host to host services. Corporates will need to supply a purpose code with high value sterling payments. Payments will not be rejected solely for missing enhanced data before end 2028 at the earliest.
Is it time to move treasury off spreadsheets? Tell me your banks, entities and payment volumes and I will give you an honest view on whether a system pays back.
Book a confidential conversation
Independent, client side help on the systems around ERP and CRM: LIMS selection, MES selection, eQMS selection, Computer system validation, HRIS selection and implementation, Payroll implementation, Workday HCM, SAP SuccessFactors, Oracle HCM, Procurement software selection, EAM software selection, WMS selection, Power BI consultancy, and ERP implementation itself. For our fees see pricing.
Written by Christopher Fagan
Managing Partner, PEF Consulting Partners
Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.
Where next