As payments, invoicing and cash positions move closer to real time, treasury is becoming one of the few corporate functions that can see money, risk and operations at the same moment.
Treasury has traditionally been defined by a fairly contained set of responsibilities: cash positioning, funding, bank relationships, foreign exchange, investments and liquidity risk. That definition is becoming too narrow. The modern treasury function increasingly sits at the intersection of payments, receivables, payables, bank balances, financing, currencies, tax, supply-chain flows and enterprise systems. As each of those activities becomes more digital and more time-sensitive, the treasury team is turning into an internal data hub almost by necessity.
The change is not mainly about giving treasury ownership of every dataset. It is about treasury becoming the point at which different financial data streams must be reconciled quickly enough to support decisions. A finance function can tolerate a monthly management report being several days old. A treasury team deciding whether to fund a payment, draw a facility, hedge an exposure or move cash between entities cannot. The closer business activity gets to real time, the greater the premium on timely, standardised and trusted financial data.
That shift is already visible in market infrastructure. SWIFT describes ISO 20022 as an open global standard that carries consistent, rich and structured financial information, with richer and more granular data moving end to end in payment messages. SWIFT source
Payments are becoming data events, not just cash movements
The most immediate driver is the modernisation of payment infrastructure. In Europe, the ECB reported that TIPS processed 2.47 billion instant payments in 2025, an 82.5% increase from 2024. Euro-denominated instant-payment value also rose sharply as implementation of the EU Instant Payments Regulation broadened usage and removed the scheme-level €100,000 value ceiling in October 2025. The ECB noted that some higher-value transactions suggest corporate adoption is beginning to expand. ECB TARGET Services Annual Report 2025
In the United States, FedNow provides participating institutions with around-the-clock instant-payment infrastructure, while its participant and service-provider directories continue to expand. The significance for treasury is not simply that funds can move faster. Faster movement changes the information cycle around cash. A payment instruction, bank balance, liquidity decision and reconciliation record are increasingly parts of the same near-real-time process. Federal Reserve - About FedNow
That makes old operating models based on end-of-day files and delayed bank statements less satisfactory. Treasury increasingly needs intraday balances, payment-status information, expected inflows, forecast outflows and exception alerts in one place. The function therefore becomes a consumer, validator and distributor of data across the enterprise.
ISO 20022 raises the value of structured treasury data
ISO 20022 matters because it changes what can travel with a payment. Structured remittance information, party data and transaction references can make reconciliation more automated and analytics more useful. SWIFT says the standard provides richer, better structured and more granular data, improving transparency and remittance information. For treasury, that can reduce the distance between making a payment and understanding what the payment represents. SWIFT - About ISO 20022
The next migration milestone reinforces the point. After 14 November 2026, SWIFT says unstructured postal addresses will no longer be accepted in CBPR+ messages; fully structured or hybrid addresses will be required. This is a technical change, but it illustrates a wider trend: the financial system increasingly expects data to be standardised enough for machines to process it reliably. SWIFT - November 2026 milestone
Treasury teams that treat ISO 20022 as a bank-connectivity project risk missing much of the opportunity. If payment data is mapped consistently to ERP records, invoice identifiers, legal entities, suppliers and customers, treasury can improve cash application, payment investigation, sanctions-screening context, working-capital analysis and management reporting. The value comes from connecting the message standard to the company's own data architecture.
E-invoicing is pulling treasury closer to commercial data
A similar convergence is occurring in invoicing. The European Union's VAT in the Digital Age package was adopted in March 2025 and is being implemented progressively through 2035. From 1 July 2030, cross-border B2B transactions will be subject to digital reporting requirements based on e-invoicing, with e-invoicing becoming the default method for invoicing in the relevant framework. European Commission - ViDA
For treasury, e-invoicing is not only a tax or accounts-receivable issue. When invoice creation, approval, payment status and settlement data become more structured, the organisation can connect commercial events to cash events more directly. That improves the quality of short-term forecasting because treasury no longer has to infer as much from historical payment patterns alone.
This is where the idea of treasury as a data hub becomes practical. Treasury may receive the bank-side truth about whether cash moved, while accounts receivable holds the invoice-side truth about what was due, procurement holds the purchase-order context, and tax holds the reporting obligation. Better outcomes depend on connecting those records rather than allowing each function to maintain a separate version of reality.
Cash forecasting is becoming a data-engineering problem
Forecasting has always been part of treasury, but the nature of the task is changing. The hard problem is no longer merely choosing a forecasting technique. It is getting sufficiently clean, timely and granular data from the business. Forecasts built from inconsistent entity codes, delayed invoice data, manually updated spreadsheets or fragmented bank feeds can create a false sense of precision.
As more data becomes available, treasury can move from a largely periodic forecasting process toward continuous revision. Bank balances can update liquidity positions; receivables data can adjust expected inflows; payroll and tax systems can update known outflows; procurement data can identify upcoming supplier payments; and market data can alter FX or funding assumptions. The treasury team's role expands from producing a forecast to governing the data pipeline that makes the forecast credible.
That does not mean every treasury department needs to become a software-engineering team. It does mean that data ownership, data definitions, interfaces and exception handling become treasury priorities. A treasury platform can automate many steps, but automation only scales trustworthy information if the underlying mapping and governance are sound.
The internal data hub changes the relationship with banks
Banks have traditionally been important information providers to treasury, supplying statements, balances, confirmations and transaction reports. As corporate systems become more integrated, the relationship is shifting. Treasurers increasingly expect banks to provide machine-readable data through APIs, ISO 20022 messages and real-time channels that can feed directly into internal workflows.
The same trend creates an opportunity for banks. Institutions that can provide high-quality transaction data, virtual-account structures, cash-position APIs, payment-status information and liquidity analytics become more deeply embedded in the corporate operating model. In that sense, data quality can become part of transaction-banking competitiveness, not merely a technical service feature.
But there is a strategic counterweight. The more treasury centralises data across multiple banks, the less dependent it may become on any one bank's proprietary portal. A well-designed treasury data layer can make providers more interchangeable because the corporate sees the relationship through its own consolidated interface. Banks may gain deeper operational relevance while simultaneously losing some control of the user interface.
Real-time information creates new control risks
More data and faster payments do not automatically produce better decisions. They can also amplify errors. An inaccurate master-data record, compromised credential or faulty automation rule can propagate more quickly in a real-time environment than in a batch process where humans had more time to intervene.
The ECB's 2025 TARGET report offers a useful reminder that speed and resilience must develop together. TIPS availability was 99.99% in 2025, but the broader TARGET environment still experienced significant incidents in T2 that required follow-up action. For corporate treasurers, the lesson is that always-on financial infrastructure increases the importance of fallback procedures, data validation and operational resilience. ECB - TARGET Services in 2025
The control model therefore has to evolve alongside the data model. Treasury needs strong entitlement management, segregation of duties, payment thresholds, trusted beneficiary data, audit trails and clear rules for automated decisions. If AI is introduced into forecasting or payment workflows, the governance challenge becomes even sharper: the organisation must know which data the system used, what action it is permitted to take and when human approval remains mandatory.
Not every company needs a centralised treasury data architecture
There is a reasonable counterargument to the data-hub thesis. Many smaller companies do not need a sophisticated enterprise treasury architecture. Their payment volumes, bank relationships and currency exposures may be simple enough that a well-controlled ERP and a small number of bank connections are sufficient. Building a large treasury technology stack can create cost and complexity without a corresponding return.
Even in large groups, centralisation can go too far. Local entities may have regulatory, tax, banking or commercial information that cannot be reduced to a single global template. Excessive standardisation can also make the organisation brittle if every process depends on one platform or one data model.
The strategic objective should therefore be interoperability rather than centralisation for its own sake. Treasury needs enough common data to see and control enterprise liquidity, while preserving local detail where it is operationally or legally necessary. The best architecture may be federated: common standards and governance, but multiple systems connected through controlled interfaces.
What this means for banks, fintechs and finance leaders
For banks, the shift increases the strategic value of transaction data and connectivity. Corporate clients will judge providers not only by pricing and credit capacity but by how cleanly their data integrates into treasury workflows. For fintechs and treasury-technology vendors, the opportunity lies in orchestration: connecting banks, ERPs, invoice platforms, market data and forecasting engines without becoming another silo.
For CFOs and boards, the main implication is organisational. Treasury can no longer be viewed only as the team that moves money after commercial decisions have been made. It increasingly becomes the function that can tell the business where liquidity is, what is expected to happen next, which exposures are building and whether financial execution matches operational reality.
That broader role also raises expectations. Once treasury becomes an internal data hub, it becomes accountable for data quality, resilience and interpretability as well as cash. The function's influence grows, but so does the importance of governance and technical capability.
Conclusion
Treasury is becoming an internal data hub because the financial operating environment is becoming faster, more structured and more connected. Instant payments compress decision windows. ISO 20022 increases the amount of machine-readable information attached to transactions. E-invoicing links commercial events more closely to financial reporting. APIs and integrated platforms make it possible to combine those data streams into a more continuous view of liquidity.
The strategic advantage is not data volume. It is the ability to turn reliable financial data into timely decisions. Companies that build that capability can forecast cash more credibly, reconcile faster, manage liquidity more precisely and respond to stress with better information. Those that merely collect more data may end up with a larger technology estate and the same uncertainty.
The treasury function is therefore moving closer to the centre of enterprise information architecture. It may never own all the data, and it should not. But as long as money remains the common language of business, treasury will increasingly be the place where many of the company's most important data streams have to agree.
References
2. SWIFT - ISO 20022: Call to action for November 2026
3. European Central Bank - TARGET Services Annual Report 2025
4. European Central Bank - TARGET Services in 2025: growth, a new launch and lessons learned
5. Federal Reserve Financial Services - About the FedNow Service
6. Federal Reserve Financial Services - FedNow Service Participants and Service Providers
7. Federal Reserve Financial Services - FedNow Service 2026 Fee Schedule
8. European Commission - VAT in the Digital Age (ViDA)
9. European Commission - VAT in the Digital Age: 2026 Work Programme
