Healthcare Mergers and Finance Operations: What to Unify Before the Close Date

Summary: What happens to finance and operations when two healthcare organizations become one? This blog explores what breaks first after a merger, where fraud and errors slip into the seams, and why the process can come together long before the ERPs do. Learn how to build a five-step day-one checklist and use one workflow layer to keep vendors paid while the systems catch up.

Healthcare M&A is back, and finance and operations teams feel it first. Hospitals and health systems announced 56 deals through the third quarter of 2026. That already tops the 46 deals announced in all of 2025. At this pace, 2026 is on track to be the most active year for hospital transactions since the pandemic began.

The deals are getting bigger, too. Mergers between organizations with more than $1 billion in annual revenue appeared for the third straight quarter. Sutter Health and Allina Health plan to form a 39-hospital system with about $26 billion in revenue. Both systems hope to close by the end of 2026, pending regulatory approval.

Most deal coverage focuses on structure, regulatory approval, and market share. Finance and operations leaders know the harder part arrives on day one. That’s when two AP processes, two vendor lists, and two approval hierarchies have to act like one organization. Vendors still expect payment on schedule, and they have no reason to wait while the integration plan catches up.

Here’s what tends to break first, where the risk hides, and what to put in place before the close date.

What breaks first when two finance teams become one

The first weeks after a close rarely match the integration plan. Each organization arrives with its own ERP, its own invoice habits, and its own idea of who can approve a $50,000 purchase. The health system routes everything through a formal chain of command, while the newly acquired clinic group approves by email. Operations leaders like clinic managers, purchasing teams, and urgent care site leads are left guessing whose rules apply.

Picture the combined AP inbox two weeks after close. A medical supply distributor appears under two slightly different names, with two remit-to addresses and two sets of payment terms. The same invoice gets paid from each legacy system, and nobody catches it until month-end reconciliation. Multiply that by every vendor the two organizations share, and the cleanup becomes a project of its own.

Four problems tend to pile up at once.

• Duplicate vendor records. The same supplier sits in both vendor lists with different remit-to addresses, payment terms, and bank details.
• Mismatched approvals. Two sets of spending limits and two groups of approvers leave no clear answer on who signs off for the combined entity.
• Scattered documents. W-9s, contracts, and invoice backup live in separate folders, inboxes, and shared drives, so nobody sees the full picture.
• Misaligned close calendars. Month-end dates rarely match, and accruals often live in separate spreadsheets that someone has to reconcile by hand.

Each one is manageable alone. Together, they turn a routine payment run into a fire drill while the controller fields the board’s first questions about integration savings. Integration work stretches across quarters, but vendors need payment every week.

The deal pipeline adds another reason to get this right. Some 61% of healthcare executives expect to increase their deal activity in 2026. That makes a repeatable integration playbook worth more than a one-time cleanup.

Not every deal is a combination, either. Divestitures made up nearly one-third of announced deals in the third quarter, and they create the reverse problem. The selling system has to carve out vendor records, open invoices, and approval rights for facilities it no longer owns. The same checklist applies, just run in the opposite direction.

Watch the seams where fraud and errors slip in

A merger hands fraudsters a convenient story. Business email compromise affected 74% of organizations in 2025, and an email announcing new bank details “after the acquisition” sounds completely plausible. With two vendor lists and two groups of approvers still in play, nobody can easily confirm which request is real.

Honest mistakes follow the same path. Fraud and errors both live in the seams of your AP process, and a merger creates new seams overnight. A supplier who always received checks from a clinic might suddenly get an ACH payment from the health system. Meanwhile, an early-pay discount slips through unnoticed.

Documents add a third layer of risk, and healthcare files go well past invoices. Finance teams also hold W-9s, business associate agreements, and GPO pricing agreements. Physician service agreements add another layer, along with the time logs that support each payment. A shared drive works for a week. It won’t hold up when an auditor asks for the trail behind a payment that crossed both organizations. When the deal adds surgery centers, bill-only implant records and consignment paperwork join the pile too.

People are the fourth risk. Every team carries habits from its legacy systems. The person who knows why a certain vendor gets paid early may now sit across the org chart. That knowledge needs a home in the process instead of in someone’s head.

The pattern across all four risks is the same. Every gap comes from work that happens outside a defined process, and a team can build that process before the close date.

Build the day-one checklist before the close date

Most of this work is decisions and cleanup, and it can start before anyone touches a system. These five steps give a newly combined finance and operations team a solid foundation.

1. Reconcile the vendor lists before you combine them. Match suppliers by tax ID, flag duplicates, and confirm bank details with a known contact before anything gets paid from a combined record. Collect W-9s and wire details up front, the same way AP teams prepare for a wave of new vendors.
2. Pick one approval hierarchy. Set spending limits, approvers, backups, and separation of duties for the combined entity. Then write them down as embedded controls a workflow can enforce. Turning those rules into repeatable workflows is the core of business process management, and it keeps approvals consistent across every facility.
3. Hold vendor bank changes for verification. Route every change request through a callback to a number already on file. A fraudster can spoof an email, but they can’t answer a phone number your team already had. Keep that rule in place until both vendor lists are clean.
4. Give documents a single home. Pull invoices, W-9s, vendor contracts, physician agreements, and bill-only records into one searchable repository with clear permissions. Clinician onboarding files can follow the same path, so HR and finance work from one set of records. Ask any platform that will store these files whether it’s HIPAA compliant and can share current SOC 1 and SOC 2 reports.
5. Set one payment calendar. Agree on which entity pays which invoices during the transition. Then tell vendors who to contact and when to expect payment. A short vendor notice saves AP from fielding the same question over and over.

ERP consolidation can take years, and it doesn’t need to happen first. The habits that break a merger are the same ones that survive a system change. That’s why it pays to fix the process before you move to a new ERP. Sorting approvals, documents, and vendor records now keeps whichever platform wins from inheriting two sets of habits.

Use one workflow layer while the ERPs catch up

The checklist raises a practical question. How does a team run all five steps without adding headcount in the middle of an integration? The answer starts with treating integration as a process problem first and a system problem second.

A shared workflow layer connects to each ERP where it already sits. One platform replaces two overlapping sets of approval tools, document stores, and AP processes. The general ledger decision can play out in the background. The combined team gets a working process long before the ERPs converge.

Here’s what that layer handles in practice.

• Approvals follow one set of rules. Configurable workflows can route every invoice and vendor request by amount, entity, and department, so acquired facilities follow the same chain.
• Documents live in one place. Intelligent capture can read invoices, contracts, and agreements from both organizations, and supporting files stay attached to each transaction for audit.
• Payments run on one calendar. Both legacy AP teams work from the same queue, so payment timing and vendor communication stop depending on who owned the supplier first.

The payoff shows up in a few places at once. Vendor bank changes follow a single verification path, which narrows the fraud exposure described earlier. Approvals move faster because everyone works from the same embedded controls. Finance and operations leaders also get one view of what’s waiting, what’s approved, and what’s paid across every location.

Starting with approvals and documents gives the integration team an early, visible win. That progress builds confidence for the harder ERP and reporting work ahead. It also gives both sides a shared way of working before the org charts settle.

Start day one with one way of working

Healthcare M&A isn’t slowing down, and the finance work behind each deal doesn’t wait for the strategy deck. Two vendor lists and two approval chains are manageable when the rules are written down and vendor records are verified before close. Documents that already live in one place turn the first audit request into a quick search instead of a scavenger hunt.

ERPs will converge on their own timeline. Approvals, documents, and payments can come together much sooner when a shared workflow layer carries them. Finance teams that get there early spend the next quarter improving the combined operation instead of repairing it.

Inherited vendors also bring compliance questions, from business associate agreements that never carried over to records with no clear retention schedule. Those gaps are covered step by step in Your AP Files Are a HIPAA Risk. Here’s What to Audit Before Year-End.

onPhase works with healthcare finance and operations teams to bring approvals, documents, and supplier payments onto one platform. That platform sits alongside the ERPs they already run. For a newly combined organization, that means a calmer first quarter and vendors who never have to notice the merger.