The healthcare industry is good at talking about payment modernization. It’s less good at actually doing it. Healthcare disbursement infrastructure remains one of the biggest reasons why modernization has stalled.
In 2024, U.S. healthcare avoided an estimated $258 billion in administrative costs through electronic transactions, according to CAQH’s 2025 Index. That is a number the industry cites proudly. What gets less attention is the footnote from Nacha: there is still a $21 billion savings opportunity sitting on the table, waiting for full automation of transactions that remain manual or only partially electronic.
Twenty-one billion dollars. Still waiting. Most of it sitting inside healthcare disbursement infrastructure that was never actually built, it was assembled.
Here is why that number is not shrinking as fast as it should: most healthcare payment operators did not build a disbursement infrastructure. They assembled one. A virtual card vendor here, an ACH processor there, a sponsor bank for this program and a different one for that program. Over years of growth and acquisition, the stack grew sideways instead of up.
The result is a disbursement architecture that looks unified from the outside and is anything but underneath.
The Vendor Sprawl Nobody Talks About
Each addition makes sense in isolation. Accumulated over time, they create an environment where a single disbursement function, getting money from a payer to a provider, can involve three or four separate vendor relationships, each with its own support line, its own dispute process, its own data model, and its own reconciliation logic.
According to J.P. Morgan’s 2024 Trends in Healthcare Payments report, 45% of surveyed providers receive virtual cards from insurers, while only 39% of payers say they issue them. That gap is not a rounding error. It reflects a disbursement chain where coordination breaks down between systems, and where the provider on the receiving end absorbs most of the friction.
Processing a single paper check can cost between $2 and $4, according to Visa. But the real cost of fragmented disbursement infrastructure is not per transaction. It is the operational overhead of managing multiple vendor relationships, the reconciliation burden of assembling payment data from disconnected systems, and the tax of having to coordinate across four partners every time something needs to change.
Why Reconciliation Breaks Without Unified Disbursement Infrastructure
Ask any finance or operations leader at a healthcare payment organization what keeps them up at night, and reconciliation is near the top of the list.
When disbursement runs across multiple vendors and bank relationships, reconciliation becomes an assembly problem rather than a reporting function. Virtual card data comes from one system. EFT data comes from another. Check and fallback payments come from a third. Tying those back to the underlying claims, across multiple payer clients and program types, requires either significant manual effort or a patchwork of integrations that carry their own maintenance burden.
ACH healthcare claim payment volume on the ACH Network grew 2,556% from 2013 to 2024, according to Nacha. The volume is there. In most organizations, the infrastructure to manage it cleanly is not.
The Innovation Tax on Fragmented Healthcare Payment Infrastructure
Fragmented infrastructure does not just create operational drag. It slows down the ability to evolve.
When a payer wants to launch a new card program, add a disbursement rail, or configure spend controls for a specific program type, they are not making a configuration change on a single platform. They are negotiating across multiple vendor relationships, coordinating integrations between systems that were never designed to talk to each other, and managing timelines that multiply with every added dependency.
ICHRA adoption among employers with 50 or more full-time employees grew 34% from 2024 to 2025, according to the HRA Council. The market is moving fast. The infrastructure underneath most administrators was not built for that pace, and it shows every time a new program has to wait on a vendor negotiation instead of a settings change.
What Breaks in a Point-Solution Model for Healthcare Disbursement
It is worth naming the structural issue directly, because it explains why adding vendors keeps failing to solve the problem: point solutions each solve for card issuing, or for ACH, or for reconciliation, in isolation. None of them own the ledger underneath.
Without a unifying ledger, fund segmentation happens at the vendor level instead of the program level. A payer cannot see, in one place, how a single disbursement moved from claim to virtual card to provider deposit. Each vendor sees its slice. Nobody sees the whole transaction. That is not a reporting inconvenience, it is the reason reconciliation takes analysts and spreadsheets instead of a dashboard.
This is a ledger problem wearing a vendor management costume.
What Consolidated Healthcare Disbursement Infrastructure Looks Like
The alternative to the patchwork is not a rip-and-replace exercise. It is consolidating the disbursement function onto a single platform: one issuing engine, one multi-rail payment capability, one embedded ledger, one reconciliation view.
That means fund segmentation at the program and provider level before a single virtual card is issued, so commingling and manual matching are structurally impossible rather than something a team policies after the fact. It means card issuing and processing that supports virtual cards, physical cards, and the controls a health plan or TPA needs, on the same platform that is already handling the ledger. And it means multi-rail orchestration, ACH, EFT, wire, RTP, and card networks routed through one system instead of stitched together across vendors, so adding a rail is a configuration decision, not a new vendor relationship.
Where this matters most: a configuration change stops requiring a cross-vendor coordination project. Launching a new program type, changing spend controls, or adding a disbursement method becomes additive to existing infrastructure instead of an architectural undertaking. The economics follow. Reconciliation becomes a real-time view instead of an assembled one. Interchange programs are simpler to manage when one platform, not four, is producing the data.
The healthcare payment industry has been remarkably good at adding vendors that only solve one problem. The $21 billion still on the table says it is time to start replacing them with infrastructure designed to solve the bigger issues. If your disbursement stack spans more vendors than your program types, that’s an infrastructure conversation, not a vendor negotiation.
Talk to Us to see how Qolo consolidates it onto one platform.
