# TMS or ERP treasury module: how to decide

Source: https://firmaadvisory.com/insights/tms-vs-erp-treasury-module
Last updated: 2026-10-01

TYPE html>         TMS or ERP Treasury Module: How to Decide | FIRMA Advisory                            [Skip to main content](#main)

By [Federico Lleonart](https://firmaadvisory.com/federico-lleonart) · Published October 1, 2026 · Updated October 1, 2026 · 6 min read

TMS or ERP treasury module? An ERP module often covers payments, bank statements and basic cash positions for a simpler group. A treasury management system adds multi-bank depth, forecasting, FX, debt and investment management. Decide on your banks, entities, currencies and team, and remember that bank connectivity drives timelines more than software does.

Finance teams that outgrow spreadsheets face the same question. Should treasury run inside the ERP the company already has, or in a dedicated treasury management system?

Both answers can be right. The decision depends less on features than on the company's banks, entities, currencies and team.

## What does an ERP treasury module usually cover?

ERP treasury modules typically handle payment files, bank statement import, bank reconciliation and a basic cash position. They sit on the same data as accounts payable and the general ledger.

That is their strength. Payments, postings and reconciliation happen in one system, with one set of master data.

Their limits appear with complexity. Many banks, many currencies, active FX hedging or detailed forecasting can stretch what a module was designed to do.

## What does a treasury management system add?

A treasury management system is built around treasury rather than accounting. It usually adds deeper multi-bank cash positioning, forecasting, FX and hedge management, debt and investment tracking, and treasury reporting.

It also adds another system to connect. Data flows between the TMS, the ERP and the banks, and each interface needs to work every day.

Cloud delivery has made treasury systems easier to start with. It has not removed the need for clear processes and a team that owns the system.

## Which factors should drive the decision?

Five factors decide most cases. Score your company on each before looking at products.

-   **Banks and accounts.** The more banks and countries, the more a dedicated system helps.
-   **FX and hedging.** Active hedging, with confirmations and valuations, favors a TMS.
-   **Forecasting.** A rolling forecast built from many sources favors a TMS.
-   **ERP landscape.** One ERP across all entities favors the module, while several ERPs favor a TMS.
-   **Team capacity.** A small team may not be able to run and maintain a separate system.

## When is an ERP module clearly enough?

Some profiles point to the ERP module with little doubt. If most of these apply, start there.

-   A single ERP across all entities.
-   A small number of banks, mostly in one or two countries.
-   Few currencies and no active hedging program.
-   A short-term cash forecast that finance can build from the ERP data.
-   A treasury team of one or two people.

The module can always be complemented later. Starting simple is a valid choice, not a compromise.

## When does a TMS clearly pay off?

Other profiles point the other way. If most of these apply, a TMS is likely worth its cost.

-   Several ERPs, often after acquisitions.
-   Many banks across several countries and currencies.
-   An active FX hedging program with confirmations and valuations.
-   Debt facilities, intercompany loans and investments to track.
-   A treasury team large enough to own and run the system.

### Worked example: an illustrative scorecard

The table scores both options for a hypothetical group on a scale of 1 to 5. The weights and scores are invented to show the method. They do not rate any real product.

| Criterion | Illustrative weight | ERP module | TMS |
| --- | --- | --- | --- |
| Banks and accounts | 25% | 3 | 5 |
| FX and hedging | 20% | 2 | 5 |
| Forecasting | 20% | 2 | 4 |
| Integration with the ERP | 15% | 5 | 3 |
| Cost and team capacity | 20% | 5 | 2 |
| Weighted score | 100% | 3.30 | 3.90 |

For this group, the TMS scores higher because of its many banks and active hedging. A group with three banks and no hedging would likely see the opposite result.

The method matters more than the numbers. Agree the weights with the CFO before vendors present, so the demonstration does not set the criteria.

## What the bank sees

From the bank side, the choice of system matters less than the connection. Banks onboard a channel and a set of file formats, whatever software sits behind them.

Each bank has an implementation team, a testing process and its own interpretation of standard formats. ISO 20022 messages still need testing bank by bank.

Banks also work through queues. A connectivity request competes with every other client's project, and documentation errors push it back.

Clients who arrive with complete documents, a named technical contact and test files ready move faster. The software vendor cannot speed up the bank's process.

## Why does bank connectivity matter more than the software?

Most treasury system projects that slip do so on the bank side. Host-to-host links, SWIFT connections and bank APIs each need setup, certificates and testing.

The ERP module and the TMS need the same connections. Choosing one over the other does not remove that work.

Plan connectivity first. The system decision can run in parallel, but the bank timeline sets the critical path.

Connect the banks in waves, starting with the ones that carry most volume. Early wins keep the project credible.

## What are the hidden costs of each option?

License or subscription fees are only part of the cost. These items often decide the total.

-   Interfaces between the TMS and the ERP, and their maintenance.
-   Bank connectivity setup and annual connection fees.
-   Internal time for configuration, testing and training.
-   Ongoing system administration as banks and entities change.
-   Upgrades of the ERP that change the treasury module's behavior.

## Which mistakes lead to the wrong choice?

Most wrong choices come from the process, not from the products.

-   Choosing on a demonstration rather than on agreed criteria.
-   Buying a TMS before the treasury policy and processes are defined.
-   Assuming the ERP module can do what the vendor's roadmap promises.
-   Ignoring bank connectivity until after the contract is signed.
-   Underestimating the team time needed to run the system.

## What should you ask vendors?

Demonstrations show what a product can do. These questions show what it will do for you.

-   Which of our banks have you connected before, and through which channels?
-   How do you handle bank-specific variations of ISO 20022 formats?
-   What does the interface to our ERP require, and who maintains it?
-   Which parts of our requirements need configuration, and which need development?
-   What does a typical support request cost, and how quickly is it answered?
-   Can we speak to a client of similar size and complexity?

## How should the selection process run?

A structured selection takes the guesswork out. These steps work for most mid-sized groups.

1.  **Define requirements.** Start from treasury processes and the policy, not from features.
2.  **Map banks and connectivity.** List every bank, channel and file format needed.
3.  **Score the options.** Use agreed weights for the ERP module and for any TMS shortlist.
4.  **Test with your data.** Ask vendors to demonstrate with your banks, entities and currencies.
5.  **Plan implementation.** Build the timeline from the banks' onboarding dates.

## When is independent advice worth it?

A system decision lasts many years, and vendors naturally favor their own product. An adviser with no vendor commission can keep the choice tied to the requirements.

Independent [treasury system implementation](https://firmaadvisory.com/financial-infrastructure-implementation) support covers the requirements, the selection and the bank side of the project. The policy the system must enforce starts with [the first treasury policy](https://firmaadvisory.com/insights/first-treasury-policy), and the controls with the [outsourced payments controls checklist](https://firmaadvisory.com/insights/bpo-payments-controls-checklist).

[](https://firmaadvisory.com/federico-lleonart)

[Federico Lleonart](https://firmaadvisory.com/federico-lleonart)

Federico Lleonart is the founder of FIRMA Advisory and its Head of Treasury Advisory. Formerly in cash management at J.P. Morgan and Barclays, he advises CFOs and private equity firms on treasury, banking and FX. [Read his full profile.](https://firmaadvisory.com/federico-lleonart)

* * *

This insight reflects general analysis and observations from FIRMA Advisory's work in treasury, banking, and cross-border financial advisory. It does not constitute investment advice, financial advice, or a recommendation in respect of any specific security, transaction, or financial decision. For analysis specific to your organization, contact us at [contact@firmaadvisory.com](mailto:contact@firmaadvisory.com).

## Continue reading

### [Cash management in 2026](https://firmaadvisory.com/insights/cash-management-2026)

From cash visibility to cash deployment.

### [Outsourced payments controls checklist](https://firmaadvisory.com/insights/bpo-payments-controls-checklist)

Controls that any payment system needs.

### [The first treasury policy](https://firmaadvisory.com/insights/first-treasury-policy)

The rules a system has to enforce.

## Discuss your financial priorities with us.

A brief, confidential conversation is the most efficient way to determine where FIRMA Advisory can support your organization.

[Book a 30 minute call](https://firmaadvisory.com/contact) [contact@firmaadvisory.com](mailto:contact@firmaadvisory.com)