Your ERP already centralises most of the data needed for sound treasury management: customer receivables, supplier invoices, open orders, payroll. Yet for the majority of European SMEs and mid-market companies, cash is still managed from a spreadsheet updated manually once a week. According to the AFP 2025 Treasury Benchmarking Survey, more than 60% of treasurers cite cash flow forecasting as their most difficult task. Manual forecasts achieve an average accuracy of only 78% at the four-week horizon, compared to 94% for tool-assisted approaches.
This guide is written for CFOs and finance directors at SMEs and mid-market companies (50 to 1,000 employees) who already have an ERP but whose treasury function remains disconnected from the rest of the finance IT stack. It covers what ERP does natively, when a dedicated TMS (Treasury Management System) becomes necessary, and how to build a robust integration architecture.
Why Treasury Remains the Weak Link in Most ERPs
The Paradox of Data That Is Present but Unused
A mid-market ERP centralises a company’s entire financial picture: aged receivables and payables, open purchase orders, recurring contracts, credit lines, loan repayments, tax payment schedules. In theory, everything needed to anticipate cash flows is already there. In practice, this data remains fragmented across accounting, procurement, and sales modules, with no dashboard aggregating it into a coherent treasury view.
The consequence is predictable: every Monday morning, the CFO exports receivables from the ERP, copies payable invoices into a spreadsheet, manually adds payroll forecasts and upcoming direct debits, and arrives at an approximate cash position for the next 30 days. This process takes two to three hours and relies on institutional memory that is inherently fragile. If the CFO is absent, no one knows exactly how much cash the company will have in its accounts in two weeks’ time.
The Real Cost of Poor Cash Visibility
Weak treasury visibility generates two categories of cost.
Direct costs: unanticipated overdrafts (bank charges and penalty interest), short-term credit lines drawn urgently at unfavourable rates, missed investment opportunities for cash surpluses due to lack of forward visibility.
Friction costs: delayed recruitment or capital expenditure decisions made out of excessive caution, strained supplier relationships through unclear payment plans, operational stress for finance teams at month-end.
For an industrial SME with £15–20 million in annual revenue, working capital optimisation enabled by better cash visibility can unlock between £400,000 and £1.2 million of trapped liquidity, according to PwC research on working capital in Europe. The business case for a properly configured ERP treasury module is clear.
What ERP Does Natively for Treasury Management
Cash Forecasting from AR/AP Ageing Data
Most enterprise ERPs offer a cash forecasting module that builds estimates from existing accounting data:
- Accounts Receivable ageing: posted invoices, their due dates, and each customer’s historical payment behaviour allow estimation of probable cash inflows at D+15, D+30 and D+60.
- Accounts Payable: invoices due with their payment dates give scheduled disbursements.
- Open order book: accepted customer orders not yet invoiced feed forecasts beyond the immediate aged balance.
- Contractual recurrences: rent, software subscriptions, loan repayments, monthly payroll.
The accuracy of these forecasts depends directly on data quality in the ERP. A poorly maintained counterparty master (duplicate customers, missing payment terms) makes forecasts unreliable. A master data audit is non-negotiable before any ERP treasury project.
Automated Bank Reconciliation: CAMT.053 and the Transition from MT940
Automated bank reconciliation is one of the highest-ROI functions in a modern financial ERP. It automatically matches incoming bank statements against accounting entries to identify uncleared transactions, detect received customer payments, and trigger dunning for genuine arrears.
For years, the reference bank statement format was MT940 (SWIFT), a text format dating back to the 1970s. This is now being replaced by CAMT.053 (ISO 20022), an XML standard that carries substantially richer data: structured payment references, originator IBAN, detailed payment reason, allocation of multiple remittances to a single transaction.
Key regulatory milestone: since November 2025, banks have been required to provide electronic statements in CAMT.053 format, replacing MT940. Some banks are granting a transition period until March 2026 (TreasuryXL, ISO 20022 migration, Kyriba ISO 20022 FAQ). If your ERP does not yet support CAMT.053, treat it as a priority item with your implementation partner: legacy MT940 parsers hard-coded into older integrations will stop working.
Multi-Currency Management and IAS 21 Revaluation
Exporting SMEs or companies with overseas subsidiaries face a currency risk that directly impacts cash. The ERP must handle revaluation of foreign-currency receivables and payables at closing rates (IAS 21) and offer real-time currency position tracking.
Tier 1 ERPs (SAP S/4HANA, Oracle Fusion, Dynamics 365 Finance) handle multi-currency natively with automatic exchange rate updates and conversion difference calculations. Mid-market ERPs (Sage X3, Infor CloudSuite, Odoo Enterprise) offer this functionality but sometimes with limitations on rate update frequency or hedge accounting support.
What the Main ERPs Offer Natively
| ERP | Native treasury module | Cash forecasting | Bank reconciliation | Multi-currency |
|---|---|---|---|---|
| SAP S/4HANA | SAP Cash Management | Advanced, AR/AP + rolling | CAMT.053, MT940, BAI2 | Full (IAS 21) |
| Dynamics 365 Finance | Bank management + Cash flow | Good, via Power BI connector | CAMT.054, MT940 | Full |
| Oracle Fusion Financials | Cash Management | Advanced forecasting | ISO 20022 native | Full |
| Sage X3 | Treasury module | Basic (AR/AP) | MT940 / CAMT optional | Good |
| Odoo Enterprise | Native treasury | Basic, limited | OFX, CAMT (v16+) | Standard |
| Infor CloudSuite | Financial Management | AR/AP + rolling | CAMT.053, BAI2 | Standard |
ERP Limits and When a Dedicated TMS Becomes Necessary
ERP handles accounting cash management well: actual flow tracking, bank reconciliation, short-term AR/AP forecasting. It reaches its limits when moving into financial treasury management: hedge instrument management, large-scale multi-entity and multi-bank consolidation, intercompany netting.
Complex financial instruments: interest rate swaps, FX options, letters of credit, commercial paper, money market instruments. Neither Odoo, Infor CloudSuite, nor Sage X3 handles these natively. SAP S/4HANA and Oracle Fusion do so via their TRM (Treasury and Risk Management) module, but at a parameterisation complexity level suited only to large enterprises.
Multi-entity and multi-bank consolidation: a mid-market group with five subsidiaries across three countries and fifteen banking relationships needs a consolidated real-time treasury view. ERP provides entity-level visibility; the group has no native consolidated view. This is precisely the territory of dedicated TMS solutions like Kyriba, ION Treasury, or Nomentia. Kyriba connected more than 3,400 enterprise clients across 170 countries in 2024, with links to more than 9,900 banks, processing $15 trillion in transactions (erp.today, Kyriba interview 2024).
13-week rolling forecasts with heterogeneous sources: robust forecasting at this horizon combines ERP data (AR/AP) with CRM pipeline, multi-year contracts, macro projections, and exceptional events. An ERP alone cannot ingest all these sources in a structured way. A dedicated TMS with connectors to CRM and planning tools can.
Intercompany netting: for groups with significant intercompany flows, netting (offsetting receivables and payables between entities) reduces the number of actual bank transfers and associated charges. This is a TMS capability, not a standard ERP function.
Common TMS-ERP Integration Architectures
Native Tier 1 Integration
Some Tier 1 vendors offer their own advanced bank connectivity integrated directly into the ERP:
- SAP Multi-Bank Connectivity (MBC): SWIFT gateway between SAP S/4HANA and banks, handling payment orders (pain.001) and CAMT statements via SWIFT FileAct or SWIFT API. Reserved for large enterprises with high transaction volumes.
- SAP Advanced Payment Management: centralised payment hub directly within S/4HANA, for groups wishing to avoid a third-party TMS.
- Oracle Cash Management with native ISO 20022 connectivity for partner banks.
This option offers the best functional coherence but creates single-vendor dependency.
iPaaS Connector for Mid-Market ERPs
For mid-market ERPs (Odoo, Sage X3, Infor CloudSuite) that lack native SWIFT or TMS connectivity, the most common approach is an iPaaS connector: Boomi, MuleSoft, or Make (formerly Integromat) to manage data flows between the ERP and the TMS or banks.
The connector synchronises AR/AP positions from the ERP to the TMS, and feeds CAMT.053 statements from banks back into the ERP for automatic reconciliation. This model works well but adds a maintenance layer to monitor at every ERP or TMS upgrade.
SWIFT / EBICS File Exchange (Still Dominant in Continental Europe)
Most continental European mid-market companies still exchange files between their ERP and banks via EBICS (the standardised banking communication protocol across the eurozone). A payment file (pain.001 in ISO 20022) is sent to the bank, and a statement file (CAMT.053) is retrieved each morning.
This architecture is robust, battle-tested, and supported by all serious ERPs. It remains dominant in continental Europe despite the rise of open banking, because it requires no bank API and works identically across all EBICS partner banks.
Open Banking APIs (PSD2): The Future of Connectivity
PSD2 theoretically enables a direct connection between the ERP and banks via standardised APIs, with no SWIFT files: the ERP queries bank balances in real time and initiates payments via API. In practice, adoption remains modest in the B2B segment. Open banking growth continues to be primarily driven by consumer fintechs, while B2B connectivity via bank APIs is still reaching maturity (Kyriba ISO 20022 FAQ). Aggregators such as Tink and Token.io are facilitating multi-bank connections for SMEs, but ERP use cases remain emergent.
Practical Case: Building a 13-Week Rolling Forecast from Your ERP
Here are the five concrete steps to build a 13-week rolling cash forecast from your ERP, without a dedicated TMS:
Step 1: Identify and qualify cash flow sources in the ERP. List all flows with a treasury impact: customer receipts (AR), supplier disbursements (AP), loan repayments, tax payment schedules (VAT, corporate tax, employer contributions), payroll. Classify them as certain flows (invoice with known due date) and estimated flows (open orders not yet invoiced).
Step 2: Clean up the counterparty master and payment terms. Forecast accuracy depends directly on configuration quality in the ERP. If 30% of your customers have no payment terms set, your forecast model rests on unreliable default assumptions. Master data audit is non-negotiable before any deployment.
Step 3: Configure forecast horizons. Three complementary horizons: short-term (D+7 to D+30, confirmed flows only, high reliability); medium-term (D+30 to D+60, probable flows based on historical payment behaviour); long-term (D+60 to D+90, modelled flows from the order book and contractual recurrences).
Step 4: Connect CAMT.053 bank statements. Forecasting without actual data is flying blind. Connect daily bank statement feeds to continuously compare actual versus forecast and identify significant variances: a customer paying early, a supplier delaying a payment.
Step 5: Build the rolling dashboard with threshold alerts. The dashboard displays the consolidated cash position by date over 13 rolling weeks. Configure automatic alerts: notification if forecast cash falls below a defined threshold (for example, fifteen days of operating costs), notification if a customer payment is more than five days overdue without being matched.
Market Solutions: ERP and TMS Comparison
| Solution | Native treasury | Bank connectivity | Integrated or partner TMS | Target |
|---|---|---|---|---|
| SAP S/4HANA + Cash Management | Advanced | SWIFT MBC, CAMT, BAI2 | SAP TRM | Large ETI, groups |
| Oracle Fusion Financials | Advanced | ISO 20022, BAI2 | Oracle ARCS | Large enterprises |
| Dynamics 365 Finance | Good | CAMT.054, MT940 | Kyriba, ION Treasury | Microsoft SME-midmarket |
| Sage X3 | Basic to intermediate | MT940, CAMT optional | Nomentia, Kyriba via iPaaS | Industrial SMEs |
| Odoo Enterprise | Basic | OFX, CAMT (v16+) | Via third-party module or Make | Growth-stage SMEs |
| Infor CloudSuite | Standard | CAMT.053, BAI2 | Via iPaaS | Mid-market manufacturers |
| Kyriba (dedicated TMS) | No (connects to ERP) | SWIFT, open banking, 9,900+ banks | Native | Multi-entity mid-market |
| Nomentia (dedicated TMS) | No | SWIFT, EBICS, bank APIs | Native | European SMEs-midmarket |
Budget and ROI: What to Expect
ERP treasury module implementation cost: between £12,000 and £65,000 depending on scope. A bank reconciliation and simple forecasting module (AR/AP) on an existing ERP can typically be deployed for £12,000 to £25,000, including configuration and training. A multi-bank SWIFT connectivity project on SAP S/4HANA sits closer to £45,000 to £90,000.
Dedicated SaaS TMS cost: from £18,000 to £120,000 per year depending on number of entities, connected banks, and active modules. Dedicated TMS solutions target mid-market groups with at least three to five entities and significant payment volumes.
Expected ROI: working capital reduction of 10 to 20% through better payment term management and automated overdue tracking; short-term credit line optimisation (fewer unexpected overdrafts, stronger bank negotiations backed by reliable forward positions); two to three days per month recovered by the CFO and finance team from manual consolidation tasks. According to Panorama Consulting (2025), the average ROI of an ERP project is 52%, with payback achieved on average in sixteen months. Finance modules — and treasury in particular — typically generate value fastest because the benefits are directly measurable in recovered cash.
Key Takeaways
Treasury management is one of the functions where ERP can deliver the most immediate and measurable financial impact. The condition: do not settle for the basic accounting module, but invest in AR/AP forecast configuration, CAMT.053 bank statement connectivity, and a treasury dashboard with threshold alerts.
For SMEs with a single entity and relatively predictable flows, ERP alone is sufficient to build a reliable 30–60 day cash view. For multi-entity mid-market groups with complex financial instruments or intensive multi-bank connectivity needs, a dedicated TMS connected to the ERP is the target architecture.
Do not start by choosing a TMS. Start by exploiting what your current ERP already contains. In most cases, 80% of cash visibility needs can be addressed without additional investment, provided existing modules are properly configured and master data is rigorously maintained.
Download our ERP evaluation grid to assess the treasury module maturity of your current solution across 30 criteria. For further reading, see our ERP total cost of ownership analysis and our 2026 ERP comparison guide to identify the solution best suited to your financial structure.
