The key components of an integrated treasury solution are cash visibility, bank connectivity, forecasting, payments, risk management, funding and investments, accounting integration, and security controls, and forecasting is where most teams feel the gap, with 70% of treasury leaders naming better cash forecasting accuracy as a top 2026 priority (Source: NeuGroup Treasury Outlook Report 2026). A core treasury system ties those pieces together so finance can see, move and protect cash from one place.
The market has also shifted under buyers’ feet. Swift’s ISO 20022 cutover happened, and then part of the follow-up timeline slipped. Treasury vendors changed owners. Stablecoins showed up in mainstream treasury platforms. This guide explains each component, what a modern platform should do in 2026, and how to judge vendors.
Key Takeaways
- Real-time cash visibility comes first; everything else builds on it.
- Bank connectivity mixes APIs, Swift and host-to-host files.
- ISO 20022 is now live for cross-border payment instructions.
- Swift has delayed the structured address deadline. Keep cleaning data anyway.
- Pick a platform by integration depth, not feature count.
What Is a Core Treasury System?
A core treasury system, usually called a treasury management system (TMS), is software that manages a company’s cash, liquidity, payments, financial risk and bank relationships in one place. It connects to banks on one side and to the ERP on the other, so the treasury team works from the same data that accounting and operations use.
Bookkeeping records what happened. A treasury system decides what happens next: where cash should sit, which payments go out today, how much currency exposure to hedge, and whether debt covenants are at risk. For a mid-size or global company with dozens of bank accounts across several countries, spreadsheets stop working long before the board asks for a daily cash position.
Key Components of an Integrated Treasury Solution
An integrated treasury solution has eight core components. Not every company needs all eight on day one, but a platform should be able to grow into them without a second system.
1. Cash visibility and positioning
The foundation. The system collects balances and transactions from every bank account, usually through prior-day statements plus intraday updates, and builds a single cash position by entity, currency and bank. Without reliable visibility, forecasting and investment decisions rest on guesswork.
2. Bank connectivity
How data and payment files move between the company and its banks. Most treasury teams run a mix of channels:
- Bank APIs for real-time balances and payment status where banks support them.
- Swift (for example through a service bureau or Alliance Lite2) for multibank reach with one standard.
- Host-to-host file connections, still common for high-volume domestic payments.
Good platforms hide that complexity and let you add a bank without a new IT project.
3. Cash flow forecasting and liquidity planning
Forecasting turns visibility into planning. The system combines actuals, ERP data such as receivables and payables, and user inputs to project cash over days, weeks and months. Many platforms now use machine learning to spot patterns and flag variances. The useful test is not the model but the workflow: who updates the forecast, how variance gets explained, and how quickly a planner can run a scenario.
4. Payments and payment factory
Treasury payments (intercompany transfers, debt service, tax and FX settlements) need tighter controls than routine accounts payable. A payment hub centralizes formats, approval workflows, sanctions screening and bank routing, and it often handles AP payment files from the ERP as well. Straight-through processing cuts manual handling and the fraud risk that comes with it.
5. FX and financial risk management
This covers exposure capture, hedge execution and tracking, valuations, and hedge accounting under IFRS 9 or ASC 815. For companies with significant foreign currency or interest rate exposure, this module often justifies the system on its own.
6. Debt, investments and intercompany
Tracking borrowings, credit facilities, covenants and short-term investments such as money market funds. Larger groups add in-house banking and netting, where intercompany balances are settled internally to reduce external bank transfers and FX costs.
7. Accounting, reconciliation and ERP integration
Every treasury event needs a journal entry, and every bank line needs to match. A strong integration posts accounting automatically to the ERP and reconciles bank statements against expected transactions, leaving only exceptions for people. If the ERP connection is weak, the treasury team ends up re-keying data, which defeats the purpose.
8. Security, controls and compliance
Role-based access, segregation of duties, multi-factor sign-in, full audit trails, and independent assurance such as SOC 1 and SOC 2 reports. Payments are the highest-risk part of the system, so approval chains, dual authorization and bank account change controls matter as much as encryption.
Essential Features of a Modern Treasury Platform in 2026
Beyond the core modules, buyers in 2026 are asking about four capabilities.
ISO 20022 readiness. The platform should create and read ISO 20022 messages natively and carry structured data through to reconciliation and screening, not translate it back into old formats.
Embedded AI that stays reviewable. Forecasting assistance, anomaly detection on payments and natural-language queries are common now. Kyriba, for example, has promoted what it calls Trusted Agentic AI across its platform. Ask how each AI feature explains its output and who approves actions.
Open APIs both ways. Treasury no longer sits at the end of the data chain. Planning tools, ERPs, data warehouses and banks all need to pull from it and push to it.
Digital asset and stablecoin support. This was niche a year ago. In April 2026, Kyriba announced a collaboration with Circle to bring USDC capabilities into its treasury platform. Most companies won’t need this yet, but it signals where vendor roadmaps are heading.
ISO 20022 in 2026: What Changed and What Didn’t
Two dates matter for treasury teams.
On November 22, 2025, Swift ended the coexistence period for cross-border payment instructions, so ISO 20022 replaced legacy MT messages such as MT103 and MT202 for in-scope traffic. Swift has since said more than 98% of payment instructions now move in ISO 20022.
The next step was meant to follow in November 2026, when fully unstructured postal addresses would stop being accepted and only structured or hybrid addresses (with at least town and country in separate fields) would pass. In mid-2026 Swift agreed to an industry request to extend that structured address migration, after many institutions said they couldn’t make the date. A replacement timeline was still pending at the time of writing. The Federal Reserve moved its related Fedwire release to November 2027.
The practical advice hasn’t changed. Clean your counterparty and vendor address data now. Structured data is what makes faster screening and automatic matching possible, and banks will eventually reject what doesn’t fit.
Core Treasury System vs ERP Treasury Module
Many ERPs, including SAP S/4HANA and Oracle, include treasury functionality. That can be enough for a single-ERP company with a modest bank footprint. A dedicated TMS usually wins when you run several ERPs, bank with many institutions across countries, need deep FX and hedge accounting, or want treasury to move independently of ERP upgrade cycles. For an older but still relevant take on when to upgrade, see this piece on upgrading treasury management systems.
Treasury Management System Vendors to Know
| Vendor | Positioning | Note for 2026 |
|---|---|---|
| Kyriba | Cloud TMS for large and mid-size enterprises | Added stablecoin (Circle USDC) and agentic AI capabilities in 2026 |
| GTreasury | Cloud TMS, payments and risk | Acquired by Ripple in a roughly $1 billion deal that closed in December 2025; runs as a Ripple subsidiary |
| ION Treasury | Broad portfolio (including Reval, Wallstreet Suite, IT2) | Range from mid-market to complex multi-entity treasury |
| SAP Treasury and Risk Management | Treasury inside SAP S/4HANA | Strongest fit for SAP-centric groups |
Shortlists vary by size, region and ERP. Treat any list, this one included, as a starting point for your own requirements.
How to Evaluate a Core Treasury System
Start with the problem you need solved in the next 12 months, then test vendors against it.
- Map your banks and accounts. Count banks, countries and connectivity channels. Ask each vendor how they would connect your top five banks and how long it takes.
- Test forecasting with your data. A demo on sample data proves little. Run a pilot on your last quarter of actuals.
- Check the ERP integration. Ask for references running your ERP version, and see how journal entries and reconciliation actually flow.
- Review controls. Ask for current SOC reports, how payment approvals work, and how bank account changes are protected.
- Ask about the roadmap and ownership. Ownership changes can shift priorities. Ask what changes for your contract and support.
Risk management sits next to all of this. For the wider framework, see this guide to treasury risk management.
Conclusion
An integrated treasury solution comes down to eight components working from one data set: visibility, connectivity, forecasting, payments, risk, funding and investments, accounting integration, and controls. Get visibility and connectivity right first. Forecasting and risk only work as well as the data under them.
In 2026, also check how a platform handles ISO 20022 data, how transparent its AI is, and how ownership changes might affect your roadmap. Pilot with your own banks and your own numbers before you sign.
Read Next
If you’re mapping your treasury and finance stack, these are useful next reads:
- Understanding Treasury Risk Management: Key Concepts and Strategies
- Is It Time to Upgrade Your Treasury Management System?
- More FinTech coverage on Coruzant
FAQs
The key components of an integrated treasury solution are cash visibility and positioning, bank connectivity, cash flow forecasting, payments, FX and financial risk management, debt and investment management, accounting and ERP integration, and security controls. Together they let treasury see, move and protect cash from one system.
A core treasury system is software that manages a company’s cash, liquidity, payments, financial risk and bank relationships in one place. It is usually called a treasury management system (TMS) and connects to both banks and the company’s ERP.
The essential features of a modern treasury platform include real-time multibank visibility, API and Swift connectivity, forecasting with scenario planning, a controlled payment hub, native ISO 20022 support, open APIs, and strong role-based security. In 2026, explainable AI and optional stablecoin support are increasingly on buyer checklists.
Yes, ISO 20022 affects corporate treasury teams because it changes the payment data they send and receive. Swift ended MT coexistence for cross-border payment instructions in November 2025. The structured address requirement planned for November 2026 has been extended, but companies should still clean address data now.
You may not need a separate treasury management system if your ERP’s treasury module covers your banks, currencies and controls. A dedicated TMS makes more sense when you run several ERPs, bank across many countries, or need advanced FX, hedge accounting and multibank connectivity.
