M&A Is Surging. Your Procurement Stack Isn’t Ready.

Global M&A activity hit $3.9 trillion through Q3 2026, up 28% year over year and the highest pace since 2001, according to LSEG data. PwC projects the full year will approach $4 trillion. That means thousands of companies have already inherited tech stacks they did not build, ERPs they do not understand, and procurement processes that contradict their own. Post-merger procurement integration is where deal value goes to die, and most organizations do not realize it until the damage is done.

The surge was concentrated in the first half of the year. Announced deals jumped 64% year over year in Q2 2026. Then Q3 slowed to $993 billion as Treasury yields rose. But here is the critical insight for procurement and operations leaders: the deals already closed in H1. The procurement integration work has barely started.

For finance, operations and procurement teams, the question is no longer whether a merger will touch their systems. It is how fast they can unify procurement operations across entities that were never designed to work together.

The conventional playbook says to consolidate your enterprise resource planning (ERP) systems first. That advice is wrong, and this post explains why.

By Lihi Lutan, Co-Founder and CEO

Co-Founder and CEO of Opstream, previously COO of StokeTalent (acq. Fiverr) and VP Operations at Taboola where she helped scale the company from $8M to $1B in revenue.

View LinkedIn profile →

The 2026 M&A Boom Is Creating a Procurement Problem

Deal volume accelerated faster than organizations could absorb. The first half of 2026 produced the most active M&A environment in over two decades. A lighter regulatory climate and buoyant equity markets fueled the surge. Private equity firms entered the year sitting on roughly $3.7 trillion in dry powder, according to Pipeline Road. And 72.9% of all US PE buyouts are now add-on acquisitions, according to Peony, which means most PE-backed companies are absorbing new entities and new tech stacks on a rolling basis.

Then Q3 arrived. Rising Treasury yields cooled deal flow to $993 billion for the quarter, down 41% from Q2, according to LSEG data reported by Reuters. But the procurement problem does not slow down when deal volume does. Every acquisition that closed in H1 still needs its procurement systems stitched together. The integration backlog is growing.

For procurement and finance teams, every closed acquisition creates an immediate operational problem. The acquired company brings its own ERP, its own vendor master, its own approval workflows and its own contract repository. None of it maps cleanly to the acquirer’s systems.

The pattern is consistent across enterprises that acquire frequently. The same vendor appears coded differently in each system. “Acme Inc.” in one ERP becomes “ACME Incorporated” in another. Entity resolution, the process of matching and merging these records, is the number one Day 1 pain point in post-merger procurement. Without it, consolidated spend analysis is impossible.

The result is predictable:

• Duplicate vendors coded differently across systems, making spend analysis impossible
• Broken approval chains where the acquired entity’s hierarchy does not match the parent’s governance model
• Zero spend visibility across entities for weeks or months after close
• Compliance gaps where security reviews, insurance validations and vendor questionnaires fall through the cracks
• Invoice volume spikes with no corresponding headcount increase; acquisitions can sharply increase invoice volume overnight

Order-to-cash and procure-to-pay workflows are typically the first to break. When procurement systems are not integrated or stabilized, downstream problems cascade into billing, cash flow, vendor management and inventory.

What Happens to Procurement Systems After a Merger?

The short answer: procurement becomes chaotic. Two organizations with different purchasing processes, different vendor databases and different ERP systems must suddenly operate as one. In practice, they rarely do.

PwC’s 2026 M&A Integration Survey found that only about one in three acquirers fully achieved all their prioritized deal thesis objectives. Procurement is a primary reason the rest fall short. When the vendor master is fragmented, approval workflows are disconnected and spend data lives in separate systems, the cost savings that justified the acquisition evaporate.

Most companies face three scenarios post-close:

• Full ERP consolidation: Migrate the acquired entity onto the parent’s ERP. This often takes more than a year and costs millions. Procurement waits in limbo.
• Parallel operation: Run both ERP systems indefinitely. Procurement teams toggle between systems, duplicate data entry and lose visibility.
• Orchestration layer: Deploy a platform that sits above both ERPs, unifying procurement workflows, vendor data and spend analytics without replacing either system.

Most organizations default to option one or two. Option three is the fastest path to operational continuity, yet it is the least discussed in the market.

Companies that acquire frequently have learned that ERP consolidation is often a myth. Global enterprises running many ERPs from serial acquisitions are not unusual. The realistic question is not “when will we consolidate to a single ERP?” It is “how do we operate effectively across the ERPs we already have?”

Why ERP Consolidation Is the Wrong Starting Point

ERP consolidation is necessary eventually. It is also the slowest, most expensive and most disruptive path to procurement continuity. Starting there is a strategic mistake.

Here is what the data shows:

• Full ERP integration often takes more than a year. Panorama Consulting’s 2024 ERP Report put the median ERP project timeline at 15.5 months.
• Only about one in three acquirers fully achieved all their prioritized deal thesis objectives, according to PwC’s 2026 M&A Integration Survey.
• Disparate naming conventions, inconsistent hierarchies and duplicated records disrupt reconciliation, delay reporting and increase audit exposure across departments.

During that wait, which often runs more than a year, procurement teams operate in a fog. They cannot see consolidated spend. They cannot enforce consistent approval policies. They cannot identify duplicate vendors across entities. Every month of delay erodes the synergy targets that justified the acquisition.

Serial acquirers face an even more pointed version of this problem. Each new acquisition adds another ERP to the stack. Some organizations shut down acquired ERPs immediately, which is fast but painful, with lost data and disrupted operations. Others keep acquired systems running for years, creating an indefinite multi-ERP reality. Neither path solves the procurement coordination problem on its own.

The orchestration layer does not eliminate the need for ERP consolidation. It removes the urgency. Procurement teams get cross-organization spend visibility, unified approval workflows and vendor management from day one, while IT plans the ERP migration on a reasonable timeline.

How to Unify Procurement Across Multiple ERPs After an Acquisition

It depends entirely on the approach. Organizations that lead with ERP consolidation often wait many months before procurement systems are stable. Companies that deploy an orchestration platform first can achieve operational procurement continuity in weeks.

Here is a realistic timeline for orchestration-first post-merger procurement integration:

• Days 1 to 14: Connect both ERPs. Map vendor masters. Establish unified intake for all procurement categories.
• Days 15 to 30: Deploy approval workflows that respect both entities’ governance structures. Enable centralized procurement with entity-specific routing.
• Days 31 to 60: Activate spend analytics across both entities. Identify duplicate vendors, overlapping contracts and consolidation opportunities.
• Days 61 to 90: Begin contract renegotiations with combined purchasing power. Establish vendor performance baselines across the merged organization.

Compare that to the traditional approach, where the first 90 days are consumed by ERP assessment and migration planning. No procurement improvements ship during that window.

Companies that complete financial consolidation within 30 days realize procurement and supply chain synergies two to three months faster than those that wait for full ERP integration. For teams building the business case for this approach, an ROI calculator can quantify the cost of delayed spend visibility in concrete terms.

The Orchestration Layer: Unifying Procurement Without Replacing Your ERPs

What Is Procurement Orchestration for Multi-ERP Environments?

A procurement orchestration platform sits above existing ERPs, unifying procurement workflows, vendor data and spend analytics without requiring system consolidation. It connects to multiple ERPs, CLMs, HRIS tools and compliance systems simultaneously. It does not replace any of them. Instead, it creates a unified data model that normalizes vendor records, contract terms, spend data and approval hierarchies across every connected system.

This approach solves the three most urgent post-merger procurement problems:

• Entity resolution: The platform automatically identifies and merges duplicate suppliers, contracts and purchase orders across systems. Same vendor coded as “Acme Inc.” in one ERP and “ACME Incorporated” in another? Resolved automatically. This is the number one integration pain point, and the orchestration layer eliminates it from day one.
• Unified governance: Approval policies, spend thresholds and compliance requirements are enforced consistently across both entities from day one, without waiting for ERP migration.
• Real-time spend visibility: Finance teams see consolidated spend across all entities, categories and vendors in a single view. No manual data reconciliation. When an acquisition sharply increases invoice volume overnight, the orchestration layer absorbs that growth without additional headcount.

Opstream connects to 120+ enterprise systems including SAP, Oracle, NetSuite, Workday and Microsoft Dynamics. For organizations running multiple ERPs post-acquisition, this means integration capabilities that work across every system in the stack, not just the primary one.

What PE Roll-Ups and Serial Acquirers Already Know

Private equity portfolio companies and serial acquirers live this problem at scale. A PE firm that acquires five companies in 18 months inherits five ERPs, five vendor databases and five sets of procurement workflows. With 72.9% of all US PE buyouts now structured as add-on acquisitions, this is the default operating reality, not an edge case. Full ERP consolidation across the portfolio is a multi-year, multi-million dollar project. Some firms never complete it.

The ones that move fastest have learned a counterintuitive lesson: stop trying to consolidate ERPs and start orchestrating above them.

PE-owned companies also need M&A and divestiture flexibility built into their vendor agreements and procurement infrastructure. A platform that locks you into a single ERP architecture makes both acquisitions and carve-outs harder. An orchestration layer that sits above the ERP stack makes both easier.

The orchestration-first approach gives PE-backed portfolio companies three advantages:

• Faster synergy capture: Procurement savings start in weeks, not quarters. Combined purchasing power becomes actionable immediately.
• Lower integration cost: No ERP migration fees, no data cleansing projects, no retraining programs. The existing systems keep running.
• Portfolio-wide visibility: Fund-level analytics across every portfolio company, every vendor and every spend category. This is the kind of visibility that drives better acquisition due diligence on the next deal.

Organizations that need to unify indirect and direct procurement across multiple entities find this approach particularly effective. It works across every procurement category: services, hardware, consulting, facilities and software. And for teams evaluating orchestration alternatives, the key differentiator is whether the platform truly connects to and normalizes data across every ERP in the stack, or simply adds a dashboard on top of one.

About the Author

Lihi Lutan

Co-Founder and CEO, Opstream

Lihi Lutan is the Co-Founder and CEO of Opstream, changing the way companies buy.

Throughout her career, Lihi built and scaled business operations at startups and large corporations. Early in her career, Lihi was with Cyota (acq. RSA Security) as a team leader and project manager before moving to Thomson Reuters and Fundtech to manage global projects. Later, Lihi joined Taboola (NSDQ: TBLA) as employee 15, as VP Professional Services and Operations, leading the department as the company scaled from $8M to $1B in revenue. Transitioning from Taboola to StokeTalent (acq. Fiverr), Lihi served as the company’s COO.

Lihi holds an LLB of Law and BSc of Computer Science from Tel Aviv University.

Connect with Lihi on LinkedIn →