What should companies evaluate beyond TMS functionality?
Implementation expertise, integration capability, treasury process knowledge, support and the vendor's ability to work with the organisation after go-live all affect the long-term value of a TMS.
Most treasury management system selections begin with a requirements list. Teams compare functionality, integrations, security, reporting, deployment models and cost. That work is necessary because treasury needs to know whether the software can support the processes it intends to run.
What receives less attention during selection is what happens after the contract is signed. A TMS still has to be configured around the company's bank landscape, ERP setup, approval model, reporting needs and operating reality. At that point, the difference between buying software and building a working treasury environment becomes much more visible.
The requirements list is only the first version of the project
A selection project turns treasury needs into boxes that can be compared across vendors. The difficulty is that real treasury processes rarely fit neatly into those boxes. A requirement such as cash visibility sounds straightforward until the implementation has to account for dozens of banks, different statement formats, local entities, account ownership and the timing of data across regions.
The same applies to payments, forecasting, financial instruments and intercompany processes. Once implementation begins, the team has to make decisions about ownership, exceptions, controls and data structures that were only partly visible during the RFP.
This is where a good implementation becomes more than technical configuration. It turns the requirements into a process that people can actually run every day.
Implementation quality determines whether the TMS fits the organisation
A TMS does not replace the operating model around it. Treasury still has to decide which processes are centralised, which remain local, who approves what, how exceptions are handled and how information moves between the TMS, ERP systems and banks.
Those decisions affect the value of the system long after go-live. If the setup reflects the real process, the TMS reduces manual coordination and creates a clearer operating model. If the implementation simply reproduces old workarounds inside new software, the organisation has changed the interface without changing much else.
That is why treasury expertise matters during implementation. The project team needs to understand not only what the software can do, but how treasury teams usually solve the problem and where an existing process deserves to be challenged.
The difficult questions are usually process questions
During implementation, treasury rarely asks only technical questions. The more important discussions concern how a process should work. Which bank data should be treated as the source of truth? How should forecast ownership be divided between central treasury and local entities? Which payment exceptions need escalation? How should intercompany positions be confirmed and settled?
These questions require context. A software specialist can explain where a setting sits, while a treasury specialist can help explain the operational consequence of choosing one setup over another.
The strongest implementation teams combine both. That reduces the burden on the customer to translate every treasury problem into technical language before a useful discussion can begin.
Integration work exposes the real complexity of treasury
Most treasury teams do not operate inside one system. They rely on ERP data, bank statements, market data, trading information and local inputs, which means the TMS becomes useful only when those sources are connected reliably.
Integration therefore deserves more attention than a simple 'yes, supported' in a requirements matrix. The project has to define what data moves, when it moves, how errors are handled and who owns the exception when something fails.
Nomentia's approach is built around this connected reality: the platform integrates with banks, ERP systems and other financial tools, while implementation specialists work with the customer from project setup through go-live. The point is not the integration claim itself, but the combination of software and people required to make the connection usable in daily treasury.
Go-live does not end the implementation questions
Treasury teams usually understand the new process much better after they have used it for several cycles. That is when real exceptions appear and when users start to see which parts of the setup deserve refinement.
A successful TMS relationship leaves room for that learning. The implementation should create a stable starting point, while the vendor and customer continue to improve the setup as usage becomes more mature.
This is especially relevant for organisations that implement in phases. A company might begin with bank connectivity and payments, then add forecasting, risk management or intercompany processes as the treasury function develops. The original design needs enough structure to support that expansion without forcing the team to start again.
The buying decision is also a people decision
Software is easy to demonstrate because the buyer can see screens, workflows and outputs. The people behind the system are harder to evaluate, yet they become much more important once the project begins.
Treasury leaders should therefore ask who will actually work with them during implementation, how much treasury experience sits in that team and how the vendor handles situations that do not fit a standard template.
Nomentia positions its TMS around software, treasury knowledge and trusted support together. That is a useful way to think about the category more broadly: the product matters, but the people implementing and supporting it shape how much of the product's value reaches the treasury team.
A better TMS evaluation asks what happens after the demo
The demo proves that the software can perform a task. The stronger selection question is what the organisation will need to make that task work in its own environment.
That shifts attention toward implementation capability, integration experience, process knowledge, support and the quality of the working relationship. Those factors are harder to score than a feature checklist, but they often determine whether users trust the system and whether the organisation actually retires the manual work it intended to replace.
A TMS is therefore not only a technology decision. It is a decision about how treasury will operate and who will help the team build that operating model.
Adoption is the point where implementation becomes real
Even a well-designed TMS only creates value when the treasury team actually uses the process that was implemented. That sounds obvious, yet adoption problems often appear when local users continue working in spreadsheets or bank portals because the new workflow feels slower, less familiar or insufficiently explained.
Implementation therefore has to include more than configuration and testing. Users need to understand why the process changed, where responsibility now sits and what the system replaces. Training works best when it is connected to the user's daily treasury work rather than delivered as a generic tour of the application. When adoption is treated as part of the implementation design, the organisation has a better chance of retiring the parallel processes that created the original problem.