Summarise the article with your AI
Here you can read:
Traditional T+1 batch reporting drops bank statements once or multiple times a day, leaving gaps in intraday and overnight treasury cash visibility. Real-time treasury changes this by moving towards continuous API-fed data, so a business can get instant visibility across all banks, entities and currencies. This shift can help eliminate unnecessary borrowing, cut an idle cash drag and allows CFOs and treasurers to make decisions based on what is happening intraday, not yesterday. This type of instant-visibility is helpful as companies grow and operate across multiple banks and currencies.
What "T+1" cash visibility means (and why it's no longer enough)
A treasury manager arrives in the office at 8am to assess cash ahead of a critical funding decision. The balances on screen reflect yesterday's close. How about overnight payments, incoming transfers and FX settlements? Not yet Invisible, as the incoming batch file from the bank has not arrived yet.
This is the classic T+1 batch model: treasury cash visibility depends on overnight bank statement files, delivered once or twice per banking day, resulting in intraday blind spots. Yet, many mid-market treasury teams still operate with roughly 24 to 48 hour delays in cross-bank cash visibility, and this gap is the root of the problem.
Traditional SWIFT MT940 or camt.053 files are typically transmitted by partner banks once, twice or sometimes three times a day. A treasurer managing multi-bank structures needs to log into various banking portals, download statements in different formats and then often rebuild the group position manually in Excel. If you've done this, you know how much work it is every single day.
Yet, the UK's Faster Payments Service processes near-instant transactions 24/7 and the EU Instant Payments Regulation mandates all payment providers offer SEPA instant transfers settling within 10 seconds. Payments should, hence, flow continuously. The Bank for International Settlements research puts a number on it: intraday liquidity usage equals roughly 15% of total daily payment values for financial institutions, or around 2.8% of GDP in each jurisdiction studied. Treasury teams on batch data can't see any of this.
What real-time treasury means in practice
Real-time treasury is treasury operating on live data. Cash balances, transaction confirmations and liquidity positions update continuously via API-based connectivity instead of overnight batch files.
Instead of receiving statements once daily, the treasury management system queries bank balances on demand and receives push notifications of movements as they occur.
The building blocks of instant connectivity
Modern platforms now allow for continuous API-based bank connectivity, intraday balance feeds, instant reconciliation and always-on liquidity visibility across entities and currencies.
SWIFT's Instant Cash Reporting API provides real-time access to account balances in ISO 20022 format, 24/7.
Real-time data vs real-time payments: not the same thing
Real-time payment rails like Faster Payments and SEPA Instant control how quickly funds move. Real-time treasury controls how quickly systems see those movements. Anyone can send instant payments but depending on the systems and processes, many are relying on batch statements to actually discover balances. A company can have neither, one, or both, but achieving true liquidity control requires unifying both.
T+1 vs real-time: A side-by-side comparison
| Dimension | T+1 Batch | Real-Time API |
|---|---|---|
| Data latency | 12-24+ hours, sometimes less | Seconds to minutes |
| Reconciliation | Usually once or twice daily | Continuous |
| Funding decisions | Typically next morning earliest | Intraday, same window |
| Idle cash risk | High (invisible until end-of-day) | Low (visible intraday) |
| Fraud detection | Sometimes 24 hours later | Near real-time detection |
| Mechanism | SWIFT MT940 and similar file batches | API connections |
The Basel Committee's framework established seven quantitative metrics banks use to monitor intraday liquidity risk. This is not what corporate treasury teams need, but benefits from real-time visibility vs. T+1 data still support better decision making and risk management.
Why the lag matters: The cost of delayed visibility
Some examples what delayed treasury can cost:
Unnecessary borrowing: A treasury team struggles to see a surplus in a subsidiary draws on credit facilities, paying interest on unneeded borrowing.
Idle cash drag: Surpluses that should be swept into overnight funds remain idle. In the current rate environment, the opportunity cost adds up fast.
Missed FX windows: Currency positions are discovered after large payments were made with cash flow forecasting and hedging opportunities are already missed.
Delayed fraud detection: A fraudulent outflow could be left undiscovered until the next morning, after funds are swept onward. Real-time visibility may allow for faster detection and stop such payments before they leave.
A day of delay is a day of decisions made on yesterday's numbers. CFOs making investment calls on yesterday's cash position are losing valuable time for effective decisions.
What moving to real-time actually requires
It's not just a software change. Here are the pieces companies actually need to address:
Modernised bank connectivity
Moving from file-based to API-based connections is what makes the change: Modern bank APIs enable on-demand queries and real-time notifications. The challenge still sometimes is coverage: mid-market companies need all banks to support the same standards for consolidated multi-bank visibility, but under open banking and PSD2 this is increasingly possible.
Process change
Real-time data changes what treasury does. The morning routine can shift from assembling data to managing exceptions and strategic decisions, dealing with questions like: Why is this account below threshold? Should we sweep? Instead of aggregating and collecting data.
Multi-bank, multi-entity structures
The transition is most valuable for companies with multiple banking relationships. A single-bank business gains little. However, a company with seven relationships across four countries in three currencies? T+1 creates systematic risk.
This is the mid-market reality: teams of one or two managing complexity designed for departments of ten, making the best tools for treasury teams one way of dealing with the increasing workload and complexity.
Is real-time treasury necessary for every company?
No. Value scales with banking complexity: number of banks, entities, currencies and cross-border exposures. An example: A UK SME with one account and domestic suppliers already has near-real-time visibility through online banking. However, a UK business with five European markets, four banking relationships in three currencies and a two-person treasury team is making funding decisions on yesterday's data daily. Every missed sweep, every unnecessary overdraft comes from T+1 visibility.
The shift toward continuous visibility is heavily corroborated by industry data. According to the 2024/2025 EY Global DNA of the Financial Controller Survey, only 17% of treasurers have complete near-real-time visibility. Furthermore, the PwC 2025 Global Treasury Survey confirms that leading organisations are actively rethinking their tech stacks, focusing heavily on API connectivity to unlock trapped cash.
When integrating these modern systems for 13-week cash flow forecasting, the architecture is designed to support predictive insights. Infrastructure is being rebuilt for real-time. The question isn't whether to follow. It's when. As instant payment rails spread, the visibility gap between T+1 and real-time will only cost more, not less.
