Real-Time Payments: Lessons from the UK

Think about what a “real-time payment” would actually mean to your organization in practice. The payment may clear in seconds, but would your enterprise resource planning (ERP) system update in those same seconds to reflect that payment? Would your treasury system? What about your reconciliation workflows? For many finance teams, the answer to all these questions is no.

What the UK Actually Proved

The UK’s foray into real-time payments nearly two decades ago didn’t just prove that real-time payments work at scale, although it did that. It also proved three points that are more fundamental about how finance operations should evolve when the underlying infrastructure changes.

1. It proved that expectations shift faster than corporate systems.

When the Faster Payments System (FPS) launched, batch processing of payments was the norm. Finance teams reconciled either daily or weekly, and suppliers expected payments to settle in three to five business days. The introduction of the FPS on May 27, 2008, enabled UK interbank payment times to fall from days to seconds. Early adopters gained a competitive advantage through instant availability of funds, but the service’s adoption was initially limited by banks’ readiness.

Early adopters also faced bottlenecks because batch-based back-office systems couldn’t process real-time payments immediately. Many relied on middleware or queued payments to perform their batch processing, which delayed operational benefits of the FPS. By slowing payment processing, legacy systems limited companies’ ability to fully utilize real-time settlements.

Some early adopters’ reports of the benefits they were achieving through FPS created new customer and supplier expectations around rapid payments across the UK. However, businesses continuing to use their legacy ERP and treasury systems were hamstrung by delays in payment initiation, limited remittance data, and batch-oriented downstream systems. Although companies that modernized end-to-end were able to achieve cash flow improvements in the neighborhood of 15 percent to 30 percent, those that didn’t saw gains only in the speed with which a transaction’s funds became available.

Transaction limits (initially £10,000) further inhibited corporate use of the FPS, as did reconciliations. Sparse remittance data made reconciliation difficult, and weekend/non–banking-hours support was limited.

All these factors combined to constrain adoption of real-time payments. And this limited participation by banks and corporates reduced the FPS’s usefulness early on. But once real-time payments reached critical mass, something changed.

That did not happen until sometime between 2015 and 2019, when the system was processing approximately 4 billion transactions annually. (By 2024, that number had reached 5 billion.) Corporate adoption reached these levels after FPS transaction limits were raised to £1 million, regulatory changes made FPS adoption more appealing, and technological improvements enabled adopters to reap the expected benefits. Once real-time payments reached critical mass, suppliers started expecting instant settlement. Customers assumed they would receive immediate confirmation of successful payment. The board wanted to see the company’s real-time cash positions. And finance teams that couldn’t deliver on these expectations started to look inadequate, even if they were doing exactly what they had done six months earlier.

Treasurers who had not already done so upgraded their systems and integrated APIs to deliver instant cash visibility, real-time reconciliation, and 24x7 operations—shifting from workaround legacy setups to a modern, always-on infrastructure.

2. It proved that data matters as much as speed.

The UK initially launched its Faster Payments System before modern payment-messaging standards existed. Payments were moving fast, but the information attached to them was sparse and unstructured. Early FPS transactions included only account numbers, payment amount, and one unstructured 18-character reference—insufficient data to perform automated reconciliations. Finance teams got the money quickly, only to spend hours figuring out what it was for, who sent it, and how to reconcile it.

The ISO 20022 payment messaging standard adds structured fields for invoices, remittance details, and payments’ purpose, enabling automated, real-time reconciliation and faster, more accurate cash application. The migration to ISO 20022 is essentially an admission that rich, structured data isn’t just a nice-to-have feature—without it, real-time payments just mean real-time chaos.

3. It proved that fraud scales with speed.

Real-time payments created real-time fraud. The same immediacy that makes instant payments valuable also makes them vulnerable: When money moves in seconds, the window to detect and prevent fraud shrinks to seconds. Batch review processes, fraud checks that take hours, and manual verification steps do not have a chance of being effective when payments clear long before fraud can be detected.

The problem is structural: If your fraud detection is slower than your payment rails, you will always be playing catch-up.

Other Markets Are Learning and Improving Fast Payments

The uncomfortable truth that the UK’s experience exposes is that most finance teams are running on infrastructure that was not designed for real-time operations. Their ERP utilizes batch processing, and their treasury system updates hourly, if they’re lucky. Their reconciliation workflows were built for end-of-day processing. So even if they implement real-time payment rails, corporate decision-making will happen in the gap between when payments are clearing and when information is available.

That gap is expensive: The Financial Conduct Authority’s multi-firm review observes that enhanced reconciliation checks and delays in payment processing “…increase delays on when payments are made … [and] significantly drain … liquidity.” This means treasurers have to meet substantial cash outflow needs while awaiting reconciled payments, increasing their working capital and liquidity requirements.​

In addition, financial technology media and treasury specialists Optimus Fintech report that delayed reconciliations distort liquidity visibility and force treasurers to overcompensate by holding inflated working capital reserves. The narrative is clear: “Without real-time visibility, treasurers overcompensate—holding excess cash in reserve. A 1 percent improvement in working capital efficiency can release millions in idle cash into strategic use.” ​

The UK’s experience shows that upgrading payment rails doesn’t fix this problem of timing. What fixes it is redesigning finance operations to match the speed of the infrastructure underneath them.

Other countries that have followed the UK’s fast-payments lead in the past 17 years have been able to resolve some of the challenges UK companies encountered. The interesting thing about being second or third is that you don’t just have to copy what worked; you can also use the first mover’s experience to learn to avoid what didn’t.

India’s Unified Payments Interface (UPI) didn’t adopt real-time payments in a vacuum. Instead, the National Payments Corporation of India (NPCI) built a faster-payments mechanism alongside unified payment messaging standards and API connectivity from day one—with the specific goal of avoiding the reconciliation mess the UK encountered. The NPCI developed standardized APIs to connect banks, corporates, merchants, and payment service providers, enabling instant payments, bulk disbursement, and real-time reconciliations. These enhancements drove the UPI to more than 18 billion transactions monthly. Then, in 2025, the NPCI introduced limits on high-frequency API calls to ensure stability while keeping bulk payments for corporates unaffected.

Brazil’s Pix instant payment system launched with ISO 20022 messaging built in, so from the platform’s introduction, it has leveraged ISO 20022’s rich data to enable seamless automation, while its fraud controls and cross-border features have boosted acceptance. Now Pix delivers instant, automatically reconciled payments with an adoption rate above 90 percent among all Brazilian companies. Even small businesses now receive and match funds instantly. As an example of the benefits, one manufacturer cut its payment costs by 40 percent and achieved same-day supplier settlements.

What All This Means for Finance Teams

If you’re a CFO or treasurer watching real-time payment systems roll out in your market, here are the key lessons you can take away from the UK’s 17-year experiment:

1. Adopt modern standards immediately, not eventually. In the United States, the FedNow and Real-Time Payments networks have used ISO 20022 from launch. Still, most banks and corporates do not yet leverage their full data fields end-to-end. Fragmented legacy systems and voluntary adoption have slowed true automation and rich data use.

If you adopt real-time payments with outdated data standards, you’ll be facing the same reconciliation problems early adopters in the UK experienced. Once you’ve contracted to roll out a treasury management system, ERP system, or banking relationship without support for ISO 20022 and API connectivity, upgrades become much more costly. Push during procurement—vendor selection, contract negotiations, and initial integrations—for full ISO 20022, API, and real-time capabilities.

2. Build fraud detection at payment speed, not review speed. Batch fraud review in a real-time–payment world is like locking your car doors an hour after someone has stolen the car. If you can’t detect and prevent fraud within seconds, all you’re doing is documenting losses.

The UK introduced liability rules after fraud exploded there. Since October 2024, UK banks have been required to reimburse most Authorized Push Payment (APP) fraud victims (up to £85,000) and share costs, shifting incentives to encourage stronger real-time fraud controls. But that can be an expensive way to learn. Set the frameworks first: Go ahead and implement dual authorization, payment limits, multifactor authentication, behavioral/real-time anomaly monitoring, and validated vendor data before you deploy real-time payments.

3. Modernize finance systems in parallel, not sequentially. Upgrading your payment infrastructure without upgrading your ERP system, treasury platform, and reconciliation workflows just moves the bottleneck, rather than eliminating it. A mismatch between your ERP and treasury management systems can cause delays, result in duplicative or lost payments, worsen the lag time for reconciliations, and lead to costly errors. Full automation and real-time benefits require your treasury and G/L systems to be aligned.

Research your options for moving to a continuous, automated, API-driven reconciliation process that will automatically match more than 95 percent of your transactions in real time, flagging exceptions instantly and enabling a same-day close.

4. Prepare for the expectation shift, because it happens fast. Once real-time payments reach critical mass, stakeholders stop accepting batch-speed answers. If your finance operations group can’t deliver that, the conversation shifts from “Why do we need this?” to “Why can’t you do this?” And that’s a much harder conversation to have.

Now’s the time—before you’ve implemented real-time payments—to invest in governance, new roles, training, updated controls, and continuous change management. Build executive oversight and robust policies for end-to-end payment processes, including policies for dealing with fraud, exceptions, and compliance.

5. Understand that first-mover advantage decays. Success isn’t about being first; it’s about being willing to continuously reinvest and modernize. If you think upgrading once is enough, you’re already behind. Treat payment modernization as a rolling program. Establish executive ownership, monitor industry changes, set a multiyear road map, conduct regular reviews, and budget for upgrades and staff training.

What Happens Between Payment and Position

For U.S.–based corporate treasury teams, the UK’s experience demonstrates that the value of real-time payments is less about making money move faster and more about closing the gap between when money moves and when finance teams can see it, trust it, and use it to make decisions. That gap—between payment speed and information speed—is where modern treasury strategy gets built or breaks down.

More importantly, the benefits of adjusting systems and processes to accommodate real-time information will extend far beyond streamlined implementation of a new payment rail. Within the next five years, your treasury team will be expected to be able to answer the question “How much cash do we have?” immediately and anytime. When you need a real-time companywide cash position, it won’t matter how fast your payments are. And if you can’t provide it, your management team will be making decisions in the dark.