Why Payments Are the First Test of Post-Merger Revenue Cycle Integration

Key Insights:

• Payment operations start running the moment a deal closes, long before systems decisions are settled
• The business office, treasury, and finance each see the same gap in a different place: the work queues, the bank, and the close
• Connecting operations across existing systems keeps every dollar accounted for without waiting on the EHR road map
• The pattern set in the first integration becomes the operating model for every acquisition that follows

Health systems working through post-merger revenue cycle integration know one thing: payment operations can’t wait. Every acquisition has a plan for them. Payments will be redirected, payers will be notified, and the seller’s business office will keep things running until the handoff. Then the money starts arriving. Some is still issued to the old organization. Some covers claims from both sides of the deal. Much of it comes through the acquired hospitals’ usual channels, in formats the parent’s systems weren’t set up to read. None of it consulted the plan.

Inside the organization, each of those payments sets off a chain of work. It has to find its way to the right hospital, the right billing system, and the right line on the books. Finance is reconciling deposits in bank accounts it has never managed before. And for a while, often longer than anyone expects, both organizations keep doing it their own way.

Whether the organization is new to acquisitions or well practiced, this is where revenue cycle integration meets its first real test. The deal model assumes the combined organization can collect, track, and report its cash as projected. The payment operation is where that assumption gets proven.

Payments Move Faster Than Systems Decisions

Part of what makes that test difficult is timing. Most integration road maps treat the EHR as the organizing decision, and much of the rest lines up behind it. That sequencing makes sense for clinical operations. For payment operations, it opens a window measured in quarters, sometimes years, in which each organization’s revenue cycle continues to run on the systems and processes it brought to the deal.

Payments don’t wait for that window to close, so even a well-built plan usually relies on a bridge: a spreadsheet that splits co-mingled payments, a shared folder of EOBs waiting on someone who knows the other system, and a month-end process that reconciles each entity separately before anyone attempts a combined view. Bridges work, and they’re often intentional. They also tend to outlast their original timeline, because the systems decisions they’re waiting on take time to settle.

Three Views of the Same Problem

How the test shows up depends on where you sit.

The work queues. For the business office or shared services team, it usually surfaces as exceptions. A payment that maps cleanly to one system posts as expected. One that spans entities, arrives on paper without familiar indexing, or carries a code that means something slightly different in the other billing system needs a closer look, and those can add up quickly.

The bank. For treasury, it tends to surface as matching. Reconciling one organization’s deposits to its cash journal and billing system is familiar work. Add a second set of accounts, a different lockbox, a different way of batching, and the occasional payment that belongs partly to each, and the same task takes on a new shape.

The close. For finance leadership, it often surfaces as timing. Cash may be arriving on schedule, but attributing it to the right entity can take longer than the close calendar allows. A deposit that isn’t yet tied to a posted payment, or a reconciling item that needs one more explanation, can make the combined picture harder to read with confidence, even when the underlying numbers are sound.

Each of these views point to the same question: how to run a connected revenue cycle across systems that remain separate.

How Health Systems Reconcile Payments After an Acquisition

Depending on the deal and the systems involved, most organizations land on one of three approaches.

Keep each organization on its own until systems align. Each entity continues to post and reconcile in the systems it already has, and finance brings the results together at month end. It is the least disruptive option in the near term, and for a short integration timeline it can be the right one. The trade-off is visibility: the combined picture arrives later, and the bridge carries more weight with each entity added.

Extend the parent’s existing process. Acquired entities route remittances and deposits into the parent’s lockbox and posting workflow. For a smaller acquisition on compatible systems, this is often practical. It gets harder when entities run different billing systems, when remittances regularly span tax IDs, or when the next acquisition arrives before the first one settles.

Connect revenue cycle operations across existing systems. Rather than waiting for every entity to share a single platform, this approach creates one process for receiving, validating, distributing, and reconciling cash across the host systems already in place. It takes thoughtful integration work and clear rules for handling exceptions. In return, finance and revenue cycle teams get a consistent operating model while longer-term systems decisions follow their own timeline.

Whichever approach fits, the work comes down to keeping every dollar accounted for. That means more than getting a remittance to the right entity. It means preserving the thread between the original remittance, the transactions it becomes in each billing system, and the bank deposit that ultimately supports reconciliation. When that thread holds, the close is easier to trust. When it breaks, it has to be rebuilt after the fact.

Four principles help keep that thread intact, and they matter most for organizations weighing the third approach:

1. One intake process across sources. ERA/835 files, lockbox deposits, paper EOBs, and payments that originate outside the EHR should all enter the same way, whichever entity they belong to.
2. Distribution and validation by rule. Remittance data should be directed to the right entity, tax ID, and host system by rules the organization defines, and validated before posting, so errors are caught before they reach downstream records.
3. Reconciliation across the full cash life cycle. The bank is the source of truth for cash, but reconciliation has to carry through from deposit to posted transaction to general ledger, so a discrepancy can be traced to where it began.
4. Visibility across the combined organization. Leadership should be able to see cash activity across facilities and tax IDs without a separate reporting project, and without waiting on the EHR road map.

The First Test Shapes the Next One

How an organization handles payments in the first months of post-merger revenue cycle integration does more than settle the current deal. It sets the pattern for every one that follows.

Getting that pattern right is a governance question as much as an operational one that comes down to three decisions. The first is how payments are assigned to each entity, tax ID, and billing system, and how those rules change as entities are added. The second is how exception workflows come together across the combined organization, so every item lands in a queue with a clear owner and a visible status. The third is how reconciliation keeps cash accurate and reporting consistent across every entity, so the close rests on numbers everyone can trust.

The payoff shows up twice. In the current integration, finance can read the combined picture with confidence sooner, treasury reconciles each entity against the same numbers, and the business office works exceptions that are already sorted and assigned. When the next acquisition comes along, that pattern is already in place: an operating model to extend rather than rebuild from the ground up.

RCMS built ReSolve® to support exactly that kind of model. Payment processing starts with a single intake workflow for every entity, whether that entity runs the same EHR as the parent organization or a different one entirely, and the rules the organization defines send each payment to the right tax ID and billing system. Reconciliation carries from the bank deposit through to the general ledger, so finance, treasury, and the business office are working from the same numbers.

Whether an acquisition is on the horizon or already underway, three questions are worth asking now. How will payments be assigned when they span more than one entity? Will the combined close rest on numbers everyone can trust? Will the next acquisition build on this one, or start from scratch?

If the answers aren’t clear yet, get in touch with RCMS about what a connected revenue cycle could do for your growing organization.