You’re doing the hard work to comply with SEPA Instant.
But there’s one thing most banks are overlooking: cash pooling.
Why does it matter?
Many banks sweep or pool leftover balances from a customer’s multiple accounts into a single master account—usually once a day, often around 7 PM.
This helps both banks and their customers manage cash more efficiently.
But with SEPA Instant Payments, customers can now send money 24/7—even after the daily sweep.
If a customer tries to make a payment late at night, their “child” account may have already been emptied. The money’s sitting safely in the master account, but the instant payment fails—because it’s not where it needs to be.
If banks don’t get this right, it’ll frustrate your customers—and become your problem too.
So what’s the issue? And how can you fix it?
The SEPA Instant cash pooling problem
Let’s illustrate the point.
Every day, Bank of Bread ran its business across different divisions.
Retail brought in a steady stream of deposits. Corporate had good days and bad. Investment mostly stayed balanced, but sometimes needed a top-up.
At exactly 7:00 PM, the bank would run the daily sweep. Funds from across the business were pulled into a central account—like clockwork.
It was efficient, predictable, and helped manage liquidity without relying on external funding.
It worked. For years.
But then 2025 happened.
SEPA Instant went 24/7. Real-time rails meant customers could move money anytime—nights, weekends, holidays. No cut-off times. No excuses.
And suddenly, the old model broke down.
At 9:30 PM, Corporate tried to send a large SEPA Instant payment. But the sweep had already emptied the account. The payment failed.
The point is this: If your customers can move money 24/7, you should not be sweeping like it’s 2012.
So, how can you fix it?
To solve this, you’ll need to rethink how cash pooling works in a real-time world.
Here are four key actions to get ahead of the problem:
1. Rethink Your Pooling Schedule
Start by re-evaluating the timing of your sweeps.
Customers are already sending payments around the clock. In fact, 99% of banks have seen out-of-hours activity since the Instant Payment Regulation came into effect. Nearly half (46%) say a substantial share of instant payments now happen outside business hours.
So, move your end-of-day sweep closer to midnight—or let customers configure it themselves.
Also consider splitting your pooling logic: one stream for interest optimisation, another for real-time liquidity.
2. Educate Customers on Threshold Management
Encourage corporate clients to set minimum balance thresholds in child accounts to cover SEPA Instant activity—even after pooling.
Offer simulation tools to help them visualise how pooling decisions affect payment availability.
3. Plan for Weekends and Holidays
Friday evening sweeps could cause real problems.
If your bank is closed over the weekend and the funds are swept out on Friday, what happens when a client tries to send a SEPA Instant payment on Saturday?
To prevent failures:
- Allow reserve balances to remain in child accounts over weekends.
- Or enable real-time intraday sweeps that adjust dynamically.
4. Enable Hierarchical Balance Validation
Upgrade your core banking system to check both the child and master account balances when a payment is initiated.
Think of it as a safety net: if the child account is empty but the master has funds, the system can still approve the payment.
This mimics liquidity coverage logic and helps ensure SEPA Instant payments don’t fail unnecessarily.
Dive in
SEPA Instant is rewriting the rules of liquidity management in Europe.
What used to be a back-office routine—end-of-day cash pooling—must now evolve into a real-time, intelligent liquidity engine.
Ignore this, and face payment failures, customer dissatisfaction, and operational strain. But if you adapt, you will deliver smarter, more resilient treasury services—fit for a 24/7 economy.
Struggling with SEPA Instant?
Speak to RedCompass Labs. We can look under the hood of your liquidity management, so you can thrive under SEPA Instant.
Share this post
Written by

Santhosh Kumar
Senior Business Analyst, RedCompass Labs
Resources