When a healthcare merger gets announced, the coverage follows a familiar script. Leadership alignment. Clinical integration. Brand consolidation. Headcount decisions. The story that gets told is about care delivery (what the combined organization will offer, and to whom).

The financial systems story doesn’t make the press release.

It’s just how it goes. ERP/NetSuite configuration, workflow logic, third-party integrations, collections infrastructure (none of it is visible until it isn’t working). And in the months after a merger closes, the back office is running on whatever the acquired company had configured for a company that no longer exists.

We know this firsthand. Because we were already in the room.

Background

Salora ERP had been supporting a mid-sized employer-sponsored primary care company on their Oracle NetSuite environment before the merger. We knew the instance. We knew the configuration history. We knew what had been built deliberately and what had accumulated over time.

When that company was acquired by a larger employer health organization (one operating primary care centers across dozens of states and serving self-insured employers at significant scale), the NetSuite environment came with it. The combined entity was meaningfully larger, more complex, and operating under a different set of demands than the system had been built to support.

Nobody paused to rebuild the ERP for the merged company. The deal closed, operations continued, and the gap between what the system was configured to do and what the organization now needed it to do started showing up (not as a single failure, but as a steady accumulation of friction).

Scope Delivered

So we closed the gaps.

When the merger closed, the NetSuite instance reflected the company that had been acquired. Not the company that now existed. The scope of work that followed wasn’t a single project with a defined end date. It was a systematic effort to bring the financial infrastructure in line with the organization operating on top of it.

Four gaps, in particular, had real operational consequences.

The Gap, in Four Parts

1. Collections Without Infrastructure (Dunning+ & Syncard)

The acquiring organization manages receivables across a large and growing employer client base. Each employer relationship carries its own billing cadence, payment terms, and escalation threshold. At the acquired company’s scale, collections follow-up could be handled with reasonable manual effort. At the combined organization’s scale, it couldn’t.

The dunning tickets that came through weren’t dramatic. A question about how dunning worked. A request for access to the module. A configuration issue. An enhancement request. Four tickets, spread across different users, each one looking routine in isolation.

Together they pointed to the same thing: the dunning infrastructure had never been configured for what the organization had become. Collections was running on whoever happened to check the aging report (not on a defined process with defined escalations).

We built it out (tiered by days outstanding, escalated by employer account type, permissioned so the right people could act without touching records they shouldn’t). The enhancement request added logic that had been handled manually. The access requests stopped recurring.

Collections now ran on a cadence. Not on attention.

2. An AP Operation That Couldn’t See Itself Clearly

On the payables side, the issues were more diffuse and more consequential. AR balances weren’t surfacing correctly on invoices. Unapproved invoices were reaching clients who shouldn’t have seen them. The AP aging report wasn’t reconciling to the trade balance sheet. Vendor payment confirmation logic was inconsistent.

None of these were catastrophic individually. Together, they described a finance team that had to do extra work to verify what the system was telling them (and couldn’t fully trust it when they did).

The fix wasn’t a single configuration change. It was a layer of work across saved searches, approval chain logic, and reconciliation tooling that gave the AP team line-of-sight into where every payment stood and what every vendor balance actually reflected. AP approvers got visibility into invoice and payment status without needing to ask. Unapproved invoices stopped moving through the wrong channels.

More importantly, we built the saved searches to make sure the fixes stayed fixed. Not just resolved (visible). The team could see the system working correctly, every day, without running a manual check to confirm it.

3. Two Systems That Had Stopped Agreeing

The organization runs Salesforce alongside NetSuite. The CRM carries the employer relationship. The ERP carries the financial record. In a well-functioning environment, they reflect the same reality. After the merger, they didn’t always.

The sync issues between NetSuite and Salesforce are the kind that build quietly. A field doesn’t update. A record shows the old entity name. Someone in finance asks why a client account looks different depending on which system they’re in. By the time it becomes a named ticket, it’s been a low-grade problem for a while.

We diagnosed the field mapping, identified where the trigger logic had broken down, and stabilized the integration. This wasn’t a reimplementation. It was precise, targeted configuration work on an integration that had been built for the acquired entity and needed to reflect the combined organization it was now living in.

When it was done, both systems agreed on what a client relationship looked like. That sounds like a low bar. In a post-merger environment, it’s not.

4. Email as a Compliance Surface

The organization uses Paubox (a HIPAA-compliant email delivery platform) to send clinical and financial communications out of NetSuite. In employer-sponsored healthcare, email isn’t a notification mechanism. It’s a compliance event. Every invoice, every approval notification, every client-facing communication carries a regulatory obligation.

The Paubox issues that surfaced were operational failures with compliance implications. Final customer emails not going through. Invoice emails not delivering. Approval notifications disappearing in transit. Each one resolved in isolation, then recurring.

The root problem was that when Paubox failed to deliver an email, NetSuite didn’t know. There was no feedback loop. Failures were silent.

We built one. A custom Webhook and RESTlet on the NetSuite side that captured Paubox delivery status in real time (failed deliveries surfaced inside NetSuite, where staff could act on them, rather than vanishing into a delivery log nobody was monitoring). We also reviewed and rebuilt the broader Paubox process configuration (not just the individual breaks) so the integration was stable rather than intermittently working.

The team could now see when an email failed. That closed the compliance gap.

What Stays With Us From This Engagement

Healthcare M&A creates a predictable and underappreciated category of risk: the acquired company’s systems come with the deal, but they were built for a company that no longer exists. The clinical integration gets planned. The systems integration gets inherited.

The patterns we addressed here aren’t unique to this merger:

• Collections infrastructure gaps appear in any organization that grows through acquisition faster than it rebuilds its AR operations
• AP visibility failures surface in any multi-entity environment where approval chains weren’t designed for the combined org structure
• CRM–ERP sync drift happens in virtually every post-merger environment where two systems of record are asked to agree without anyone maintaining the agreement
• Third-party integration fragility (particularly for compliance-sensitive tools like Paubox) is a recurring problem when integrations built for one entity’s configuration are inherited by a larger one

These are solvable problems. But they require someone who knows what the system was before, what it needs to be now, and how to close the distance between the two.

That’s the work we do.

If you’re navigating a post-merger NetSuite environment (or inheriting one) we’d welcome a conversation.

We are a financial systems integration firm specializing in NetSuite ERP for healthcare, life sciences, and high-growth businesses. 📧 [email protected] · 🌐 saloraerp.com · 📞 +1-720-254-1320