Commercial clients are not asking their banks for a longer feature list.
They are asking for control.
They want to see where cash sits in real time. They want account structures that match how their business actually operates. They want automated sweeps, faster reconciliation, and fewer manual workarounds. And they want all of it from the bank relationship they already have.
That is why virtual account management has become such an important conversation in commercial banking.
But this is also where many banks get into trouble.
A growing number of institutions now say they offer virtual account management. What many commercial clients discover later is that the experience stops at visibility. They can see more, but they still cannot move faster, automate more, or operate with the precision their treasury teams need. The result is frustration, manual work, and a growing sense that the bank is behind.
This is not just a product gap. It is a client retention problem.
When a commercial client cannot get the control, visibility, and operating flexibility they need from their bank, they start looking elsewhere. Sometimes that means moving workflows to a fintech. Sometimes it means splitting treasury activity across multiple providers. Either way, the bank loses ground in one of the most important relationships it has.
What Commercial Clients Are Actually Asking For
The modern commercial client usually is not asking for “virtual accounts” in the abstract. They are asking for outcomes.
They want:
- Real-time cash visibility across business lines, entities, customers, or locations
- Faster reconciliation without waiting for end-of-day files and manual spreadsheet cleanup
- Automated sweeps, allocations, and rule-based money movement
- Cleaner account structures that reflect how treasury actually operates
- More autonomy for business units without losing central control
- Less operational drag from exceptions, one-off requests, and batch-driven processes
This is especially true for commercial clients with more complex operating models. Marketplaces, franchise systems, escrow-heavy businesses, healthcare administrators, and vertical software platforms all need account structures that do more than report balances. They need infrastructure that can segment funds, support automation, and keep operations moving without constant intervention.
That is the real expectation gap in commercial banking today. Clients are asking for operating capability. Many banks are still delivering reporting improvements.
Why Most Banks Still Cannot Deliver It Yet
Most banks are trying to meet modern treasury expectations on top of infrastructure that was never designed for this level of flexibility.
Legacy cores are good at maintaining traditional account structures. They are not built to support dynamic hierarchies, event-driven sweeps, or real-time operational logic at the sub-account level. So banks often respond by layering on something that looks like virtual account management without actually changing what the client can do.
That is why the term VAM can hide such different realities.
From the client’s perspective, there are really three types of VAM.
The Three Types of VAM
1. “Active VAM” (Core-Facade VAM): The Illusion of Control
The most basic form of what gets labeled “virtual account management” is what we can call Active VAM or Core-Facade VAM. Think of it like this: it looks like you have multiple distinct bank accounts but behind the scenes it’s still just old-fashioned core accounts. These old-fashioned core accounts are actually traditional physical accounts, typically demand deposit accounts held at a physical bank.
This approach essentially involves grouping or relabeling existing core accounts to create a visual hierarchy. The bank’s interface might show balances for different “virtual accounts” but these are not truly segmented. It’s a reporting layer a facade placed on top of the bank’s traditional core system. There is no true virtual sub-ledger.
Because all actions still rely on the bank’s core system this model is bound by the same old constraints: batch processing cycles strict cutoff times and rigid product structures.
The Customer Experience
For the end users, the feeling is one of disappointment. “I can see more but nothing actually works differently.” They get a better view of their cash positions but they can’t act on that information in real time. Money movements still require manual requests or nightly batch processes. There is no account-level treasury automation. The structure is inflexible limiting their ability to tailor accounts to specific client needs or business units. The result is continued high operational overhead behind the scenes. This often leads to data silos, making it difficult to access unified financial information.
Use Cases That Break Active VAM
The limitations of this model become obvious when applied to modern business models.
- Marketplaces: A platform might want to show each seller their individual “account” balance on a dashboard. But with Active VAM all incoming funds land in a single core account. The platform must then redistribute those funds to sellers manually or through a slow batch process.
- Franchises or Multi-location Retail: Each store location appears to have its own account for daily deposits. However the actual cash is pooled in one central account. Moving funds for payroll or vendor payments requires manual sweeps.
- Vertical SaaS Platforms: These platforms need scalable sub-ledger accounting driven by APIs to create accounts for their customers on the fly. Core-facade VAM simply cannot support this kind of dynamic high-volume account creation.
The impact on operations is severe. Exception rates remain high as manual processes persist. Finance teams are forced to rely on “shadow spreadsheets” to track what’s really going on. Ultimately banks offering only a facade cannot support the platform-based business models that are driving economic growth. These limitations can disrupt the whole process of treasury management and payment operations.
2. Surrogate VAM: Real Virtual Accounts With No Power
The next step up is Surrogate VAM. Here the bank provides true virtual accounts created within a separate ledger. This is a significant improvement because it allows for genuine internal segmentation and reporting. Balances held in these virtual accounts accurately reflect sub-ledger positions, and these sub ledgers allow organizations to manage multiple accounts efficiently within a single system. It’s an ideal solution for tracking funds across different clients divisions or specific payment flows.
There’s just one major problem: these virtual accounts are for visibility only. They can’t do anything. They have no unique account numbers or external identifiers. They cannot receive inbound payments directly nor can they initiate outbound payments. All money movement must still occur through the parent physical account.
The Customer Experience
The customer experience is one of partial satisfaction mixed with frustration. “I can finally see the breakdown… but I still can’t automate or control it.” They have perfect visibility into their balances which is a huge step forward for reconciliation and reporting, as it also streamlines cash reporting and helps generate reports more efficiently. But they have no operational autonomy. They are still completely reliant on manual actions or scheduled processes to actually move money.
Use Cases That Hit a Wall
This model provides clarity but falls short when action is required.
- Healthcare Third-Party Administrators (TPAs): A TPA can use virtual accounts to track patient co-pays or claim-level balances perfectly. But they cannot trigger a payment to a provider or release funds to a patient directly from that virtual account.
- Corporate Liquidity and Cash Pooling: A corporate treasurer can view balances for each subsidiary in real time. But they cannot automate sweeps between those virtual accounts or enforce dynamic spending limits at the sub-account level.
- Marketplace or Gig Economy Payouts: A platform can display each gig worker’s earnings in their individual virtual account. But when it’s time for payout the platform cannot initiate payments directly from those accounts.
The operational impact is a mixed bag. Visibility improves the precision of financial tracking and reduces some manual reconciliation work. However the system still requires humans or batch logic to execute transactions. It cannot support time-sensitive use cases that require immediate automated action which limits its value for a growing number of businesses. The lack of automation can hinder risk mitigation by increasing exposure to financial risks and can also create additional tax implications for organizations, as manual processes may complicate tax reporting and compliance.
3. Full Operational VAM: Virtual Accounts That Actually Function
This brings us to the ultimate goal: Full Operational Virtual Accounts. This is the B2B infrastructure that modern businesses need. With this model each virtual account is a real functional account with its own address rules and autonomy.
An operational virtual account has a unique identifier like an account number or VA ID. It can receive inbound payments directly from external sources. It can originate outbound payments. It can hold balances run rules and automate movements independently of the bank’s core system constraints. These accounts are driven by a programmable ledger layer that allows them to be scaled up or down dynamically per client per transaction or per event. Operational VAM enables organizations to centralize cash and design flexible virtual account structures tailored to their specific treasury and financial management needs.
Qolo’s platform is built to deliver this full operational capability. It provides a real-time programmable ledger that unifies virtual account management card issuing and money movement across multiple rails.
The Customer Experience
This is where the magic happens. They get both visibility and real-time action. Each virtual account behaves like a fully functional operating account, and an automated system can streamline payments and treasury workflows by replacing manual processes and improving efficiency. Workflows for sweeps fund routing allocations and approvals can be completely automated. The result is treasury precision at scale.
Use Cases Unlocked
Full operational VAM unlocks the potential of modern platform business models.
- Marketplaces: Each seller gets an operational virtual account. Incoming payments from buyers are automatically allocated to the correct seller’s account. The platform can programmatically capture its fees and sellers can trigger instant payouts based on predefined rules.
- Franchise Models: Each store has its own operational VA. End-of-day sweeps to a central corporate account are automated. Divisional profit and loss statements instantly align with actual cash positions.
- Franchise Models (continued): Real-time visibility into cash position and liquidity buffers enables better financial planning and risk management, ensuring that businesses can optimize working capital and maintain sufficient liquidity for operations.
- Escrow or Claims Flows: Complex multi-step review processes can be built directly into a flow. Money can be held in a virtual account and released automatically based on events or thresholds.
- Corporate Treasury: A treasurer can create a sub-account for each division product line or region. Liquidity management is automated and access can be controlled on a granular level for each business unit.
The operational impact is transformative. Manual steps are removed. Exceptions are dramatically reduced. Treasury becomes a proactive strategic function rather than a reactive one. For banks this means they can finally support modern platform-based business models without a risky and expensive overhaul of their core systems.
What Banks Should Promise Instead
The right promise is not “we offer VAM.”
The right promise is: we can help you give commercial clients real-time visibility, real operating control, and modern account structures without forcing a core replacement project.
That is a much stronger answer because it speaks to the actual concern inside the bank.
Commercial teams need better tools to retain and grow treasury relationships. Product teams need a way to modernize without taking on a rip-and-replace program. Operations teams need fewer exceptions, fewer manual processes, and better control.
Banks do not need a cosmetic overlay. They need a way to close the gap between what clients now expect and what legacy infrastructure can actually support.
What It Takes to Deliver That: Quantum Ledger + VAM
This is where Qolo’s approach is different.
Qolo combines Quantum Ledger with virtual account management to give banks a modern operating layer on top of the core they already have. No rip and replace of your core.
That matters because the challenge is not just account display. It is real-time fund visibility, segmentation, reconciliation, and rules-based movement across complex commercial relationships.
With Quantum Ledger + VAM, banks can support:
- Virtual account hierarchies that mirror how commercial clients structure funds
- Real-time balance visibility and reconciliation at every level
- Automated sweeps, allocations, and routing logic
- Greater precision without opening a new physical account for every entity or use case
- A more modern treasury experience without forcing a core migration
In other words, banks can deliver the operating model commercial clients are already asking for, while protecting the infrastructure and relationships they already own.
For readers who want the product view, see Qolo’s virtual account management platform.
Proof That This Is Already Live At Commercial Banking Scale
KeyBank has already brought this model to market. Qolo’s work behind KeyVAM shows that real-time VAM at commercial banking scale is operational now, not just a roadmap concept. For more context, see the KeyBank case study and the KeyVAM launch announcement.
The Real Question Banks Should Be Asking
The question is no longer whether a bank can say it offers virtual account management.
The real question is what those virtual accounts can actually do.
If they only improve visibility, the bank is still leaving commercial clients short of what they need.
If they enable real-time control, automated movement, cleaner segmentation, and better treasury workflows, the bank is in a much stronger position to keep and grow those relationships.
That is the difference between a feature claim and a retention strategy.
And that is why the three types of VAM matter.
They do not just describe product architecture. They explain why some banks are still disappointing commercial clients, and why others are finally in position to deliver what those clients have been asking for all along.
If you are ready to assess your VAM capabilities, Qolo is here to help.
