The First 100 Days After an Acquisition: A Procurement Integration Playbook

The deal closed. The press release went out. And somewhere in the acquired company sits an ERP with a vendor master that does not match yours, approval workflows built for a different org chart, and invoice volume about to spike with no additional headcount to absorb it. Global M&A activity hit $3.9 trillion through Q3 2026, according to LSEG data. Only about one in three acquirers fully achieved all their prioritized deal thesis objectives, according to PwC’s 2026 M&A Integration Survey. The difference between the deals that capture procurement value and the ones that do not comes down to what happens in the first 100 days after close.

This is not a theoretical framework. It is a phased, week-by-week playbook for procurement and finance leaders who need to integrate procurement operations across two (or more) entities without waiting 18 months for an ERP migration to finish. It is built on patterns observed across enterprises that acquire frequently, from PE portfolio companies running serial add-on strategies to global corporations absorbing new business units into complex, multi-system environments.

If you completed your procurement due diligence checklist during the diligence phase, you have the raw material. Now you need the execution plan.

Why the First 100 Days Determine Whether You Capture Procurement Synergies

Procurement synergies are the most tangible value lever in any acquisition. Volume consolidation, vendor rationalization, contract renegotiation: these savings are quantifiable and often appear in the deal model. But they erode fast when the integration stalls.

Research from Treasure Coast Procurement suggests that roughly 20% of procurement benefits are capturable in the first 100 days, with 70% achievable within the first year. That front-loaded window exists because the organizational willingness to change is highest immediately after close. Six months later, integration fatigue sets in, attention shifts to the next quarter’s targets, and the procurement synergy line items quietly become “deferred.”

The pattern across serial acquirers is consistent. Organizations that stand up a unified procurement operating model within the first 100 days lock in those early wins and build the infrastructure to capture the remaining 80% over the following year. Organizations that spend the first 100 days debating ERP consolidation timelines capture almost nothing.

The math is straightforward. If a $500 million acquisition has a procurement synergy target of 3% to 5% of combined addressable spend, every month of delay costs hundreds of thousands of dollars in unrealized savings. Multiply that across a PE portfolio running five or six add-ons per year, and the cost of slow integration becomes a portfolio-level problem.

What Should Procurement Do on Day 1 After an Acquisition Closes?

Day 1 is not symbolic. It is operational. The moment the deal closes, the acquiring company is responsible for every purchase order, every vendor payment and every compliance obligation across both entities. The first 24 hours set the tone for the entire integration.

Here is what should happen on Day 1:

• Freeze non-essential vendor changes. No new vendor onboarding, no contract modifications, no payment term changes in either entity until the procurement team has a unified view. Critical exceptions (safety, legal, contractual obligations) proceed with explicit approval from the integration lead.
• Appoint a procurement integration lead. This person owns the 100-day plan. They report to the CFO or CPO and have decision-making authority across both entities. Without a single accountable owner, procurement integration drifts.
• Communicate to suppliers. The top 50 vendors by spend in both entities should receive a notification on Day 1: the acquisition has closed, procurement continuity is the priority, and a relationship review will follow in the coming weeks. Silence creates uncertainty, and uncertain vendors start renegotiating preemptively.
• Secure system access. The integration team needs read access to the acquired entity’s ERP, accounts payable data, vendor master, contract repository and approval workflow configuration. IT should provision this on Day 1, not Week 3.
• Establish emergency approval authority. Until unified approval workflows are deployed, define temporary spending authority for the acquired entity that mirrors the acquirer’s risk thresholds. Nothing should go unsigned for lack of a clear approver.

The most common Day 1 failure is inaction. Teams assume there is time to plan. There is not. An acquisition can sharply increase invoice volume overnight with no additional headcount. If the approval chain is unclear, invoices stack up, payment terms are missed, and vendor relationships sour before the integration has even started.

Days 1 to 14: Stabilize and Assess

The first two weeks are about preventing damage and gathering intelligence. You are not optimizing yet. You are making sure nothing breaks while you build the foundation for everything that follows.

Extract and Inventory Spend Data

Pull accounts payable data from the acquired entity’s ERP for the trailing 12 months at minimum, ideally 24 to 36 months. You need vendor name, amount, category (if coded), cost center, payment terms and invoice count. If the acquired company runs on a different ERP than yours, which is nearly always the case, do not wait for a data migration. Extract what you can and normalize it offline.

The same vendor will appear under different names, codes and structures across every 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 need. Without it, you cannot see consolidated spend, you cannot identify overlapping vendors, and you cannot quantify the synergy opportunity.

Map the Acquired Entity’s Procurement Landscape

Document the current state before you try to change it:

• Who approves what? Map the delegation of authority matrix. How are spend thresholds set? Who has purchasing authority for each business unit?
• Where do contracts live? File shares, a CLM tool, email inboxes, filing cabinets? Catalog the repository.
• Which vendors are critical? Identify the top 20 vendors by spend and the top 10 by operational criticality (which may be different lists).
• What is the technology stack? Document the ERP, any procure-to-pay tools, sourcing platforms and analytics capabilities. Note the ERP version, customization level and integration points.
• What compliance obligations transfer? Review vendor insurance tracking, security assessment cadence and any regulatory reporting that now falls on the combined entity.

Conduct a Vendor Contract Triage

You cannot review every vendor contract in two weeks. But you can triage the ones that matter most. Focus on contracts with:

• Change-of-control clauses that allow the vendor to terminate or renegotiate. These are time-sensitive and may have notification windows.
• Auto-renewal dates in the next 90 days. Missing a cancellation window locks the combined entity into terms you did not negotiate.
• Exclusivity or non-compete provisions that may conflict with the acquirer’s existing vendor relationships.
• Minimum purchase commitments that create financial liabilities if the combined entity’s demand patterns shift.

AI Document Comparison can accelerate this review significantly. Rather than reading hundreds of contracts manually, technology that compares terms against a standard template flags deviations and high-risk clauses automatically.

Days 15 to 30: Unify Vendor Data and Establish Governance

By the end of Week 2, you should have raw data and a map of the acquired entity’s procurement landscape. Weeks 3 and 4 are about making that data usable and standing up the governance framework that will carry you through the rest of the 100 days.

Complete Entity Resolution Across Vendor Masters

This is the critical technical milestone. Entity resolution merges duplicate vendor records across systems into a single, normalized view. Until this is done, every downstream activity (spend analysis, vendor rationalization, contract consolidation) is unreliable.

In multi-ERP environments, the scale of the problem is significant. Global enterprises with many ERPs from serial acquisitions commonly run five SAP instances alongside Oracle, Navision, Business One and other systems. Different instances and clients across entities mean the same vendor can appear dozens of times under different identifiers. An orchestration platform that performs entity resolution automatically across connected systems can compress this from a months-long data cleansing project into a task measured in days.

Deploy Unified Approval Workflows

The temporary emergency approval matrix from Day 1 needs to become a real governance framework. This means deploying approval workflows that:

• Respect both entities’ organizational structures while enforcing the acquirer’s risk thresholds. The acquired entity’s department heads should still route requests, but spend limits, compliance checks and escalation paths follow the parent’s policies.
• Cover every procurement category. Not just software or IT purchases. Services, hardware, consulting, facilities, and every other spend category need clear routing. Organizations that default to a narrow definition of “procurement” discover months later that a large share of addressable spend was flowing outside the governance framework.
• Work across both ERP systems. If the acquired entity is still running its own ERP (which it will be), approval workflows must execute regardless of which system originates the request.

For organizations running a centralized procurement model, this phase also means defining how the acquired entity’s purchasing activity routes into the central function. For decentralized models, it means ensuring consistent policy enforcement even when purchasing authority is distributed.

Establish a Single Intake Channel

Every procurement request across both entities should flow through a single intake channel by Day 30. This does not mean everyone uses the same ERP. It means there is one front door for purchase requests, regardless of which back-end system processes the order. Unified intake provides immediate visibility into demand, prevents rogue spending and creates the data pipeline for the spend analytics that come in the next phase.

Days 31 to 60: Deploy Spend Analytics and Identify Quick Wins

With unified vendor data and a governance framework in place, the integration shifts from stabilization to value identification. This is where the procurement team starts justifying the acquisition’s synergy targets with real data.

Activate Cross-Entity Spend Analytics

Consolidated spend reporting across both entities should go live in this window. The report should answer five questions:

• What is total addressable spend across the combined entity, by category, by vendor, by business unit?
• Which vendors do both entities share? Overlapping vendors are the primary source of quick-win savings through volume consolidation.
• Where do pricing discrepancies exist? Different business units paying different rates for the same items from the same vendors is one of the most common findings in post-acquisition spend analysis. The discrepancies are invisible until you have a unified vendor master and spend view.
• What is the maverick spend level? Purchases outside contracted terms or approved channels erode negotiated savings.
• Which contracts expire in the next 6 to 12 months? These are immediate renegotiation opportunities where the combined entity’s purchasing power can be leveraged.

For teams that have not yet achieved cross-organization spend visibility, this is the milestone that unlocks everything else. Without it, synergy tracking is guesswork.

The pricing discrepancy problem deserves special emphasis. When different business units have been operating independently, often for years, they negotiate their own rates with the same suppliers. One entity pays one rate for cloud hosting. The acquired entity pays a different rate for the identical service from the identical vendor. These discrepancies are invisible until the vendor master is unified and spend data is consolidated. Surfacing them is one of the highest-value outputs of this phase.

Prioritize Quick Wins

Quick wins in procurement integration fall into three categories:

• Volume consolidation with shared vendors. Where both entities buy from the same supplier at different prices, negotiate a single agreement at the better rate (or a new rate that reflects combined volume). These conversations can start immediately once spend data confirms the overlap.
• Elimination of redundant vendors. Two vendors providing the same service to different entities can often be consolidated to one. The savings come from both unit pricing and reduced vendor management overhead.
• Payment term optimization. Aligning payment terms across entities can unlock working capital. If the acquirer negotiates net-45 and the acquired entity operates on net-30, harmonizing to the acquirer’s terms frees cash flow.

Quick wins serve a dual purpose. They generate real savings that justify the integration investment, and they build credibility with the CFO and board for the larger synergy capture plan that follows.

Address the Invoice Volume Spike

One of the most underestimated operational impacts of an acquisition is the sudden increase in transaction volume. An acquisition can sharply increase invoice volume overnight with no additional headcount to process the extra invoices. If the acquirer’s AP team was already at capacity, the acquired entity’s invoices either queue up (missing payment terms and damaging vendor relationships) or get processed without adequate review (creating compliance exposure).

This is the point in the integration where manual procurement processes break. If the acquired entity runs on spreadsheets, email-based approvals and tribal knowledge, the combined transaction volume will expose every weakness in the process. Automation is not a nice-to-have at this stage. It is an operational necessity. A platform that handles intake, routing, approval and PO creation across both entities absorbs the volume increase without proportional headcount growth.

Days 61 to 100: Capture Synergies and Build the Operating Model

The final 40 days of the playbook shift from identification to execution. Vendor renegotiations should be in progress, the synergy tracker should be live, and the procurement operating model for the combined entity should be documented and approved.

Execute Vendor Renegotiations

Armed with consolidated spend data, the procurement team should have an active renegotiation pipeline covering:

• Top overlapping vendors where combined volume triggers better pricing tiers
• Contracts expiring in the next 6 months where the renewal is an opportunity to renegotiate with combined leverage
• Vendors with pricing discrepancies across entities, where one business unit is paying significantly more than another for the same goods or services
• Tail spend consolidation where dozens of small vendors can be rationalized to preferred suppliers with volume discounts

The first closed renegotiations during this window are critical. They provide concrete evidence that the post-acquisition procurement playbook is working and that synergy targets are achievable. Track every dollar of realized savings against the deal model’s synergy projections.

For PE-owned portfolio companies executing add-on strategies, this renegotiation phase compounds with each acquisition. The combined purchasing power of the platform company grows with every add-on, and each subsequent acquisition makes the existing vendor relationships more valuable. With 72.9% of US PE buyouts structured as add-ons, according to Peony, this compounding effect is the procurement rationale behind the entire roll-up strategy.

Build the Synergy Tracker

By Day 70, a live synergy tracker should be reporting to the CFO and the board (or PE sponsor). The tracker should include:

• Identified synergies (opportunities surfaced through spend analysis)
• In-progress synergies (renegotiations and consolidation efforts currently underway)
• Realized synergies (closed negotiations with confirmed savings)
• At-risk synergies (projected savings that may not materialize on the original timeline)

The tracker converts procurement integration from an operational project into a financial reporting function. This is what keeps the work funded and resourced beyond Day 100.

Document the Unified Procurement Operating Model

The 100-day playbook creates the foundation. The operating model makes it permanent. By Day 100, the combined entity should have a documented procurement operating model that covers:

• Governance structure: Who owns procurement across the combined entity? How are category strategies set?
• Technology architecture: Which systems run procurement? How do they connect? What is the long-term platform roadmap?
• Policy framework: Unified approval thresholds, vendor management standards, compliance requirements
• Performance metrics: KPIs for cost savings, cycle time, vendor performance, contract compliance and maverick spend

For organizations evaluating the cost and benefit of this approach, an ROI calculator can model the financial impact of faster procurement integration against the alternative of waiting for ERP consolidation.

Coordinate Across Functions

Procurement integration does not happen in a vacuum. By Day 100, the procurement team should have working relationships and coordination mechanisms with four other functions:

• Finance: Chart of accounts mapping, AP consolidation, intercompany transaction handling and budget re-alignment for the combined entity
• Legal: Contract novation for vendors that require formal assignment, change-of-control notification compliance and policy harmonization
• IT: System access management, SSO provisioning for shared procurement tools, data security protocols for cross-entity vendor data and the longer-term ERP roadmap
• Operations: Business continuity for procurement-dependent operational workflows, supply chain coordination across newly combined manufacturing or service delivery footprints

The operating model document from the previous section should include a RACI matrix that defines ownership for procurement-adjacent activities across these functions. Without it, integration gaps emerge at the boundaries between teams, exactly where post-merger friction is highest.

Do You Need to Consolidate ERPs Before Integrating Procurement?

No. And this is the single most consequential strategic decision in the entire 100-day playbook.

The conventional wisdom says ERP consolidation comes first. Migrate the acquired entity onto the parent’s ERP, then unify procurement. That logic sounds clean in a boardroom presentation. In practice, it means procurement often waits more than a year for the ERP team to finish, while every month of waiting erodes synergy targets. Panorama Consulting’s 2024 ERP Report put the median ERP project timeline at 15.5 months. Gartner predicts that by 2027, more than 70% of recently implemented ERP initiatives will fail to fully meet their original business case goals. Tying procurement integration to that timeline is a compounding risk.

The alternative is an orchestration layer: a platform that sits above existing ERPs and unifies procurement workflows, vendor data and spend analytics without requiring system consolidation. This approach decouples procurement integration from ERP migration entirely. Procurement teams get unified visibility and governance in weeks. IT plans the ERP consolidation on its own timeline.

This is not a hypothetical trade-off. It reflects the operating reality of enterprises that acquire frequently. As our post-merger procurement integration analysis details, companies running many ERPs from serial acquisitions are not unusual. The question for these organizations is never “when will we consolidate to a single ERP?” It is “how do we operate effectively across the ERPs we already have?”

The Two Approaches: Shut Down Acquired Systems vs. Keep Them Running

In practice, acquirers take one of two paths with the acquired entity’s ERP and procurement systems. Both have trade-offs, and neither solves the procurement coordination problem on its own.

Approach 1: Shut Down the Acquired ERP on Day 1

Some acquirers immediately shut down the acquired company’s ERP and migrate everything to the parent’s system. This approach is fast but painful. The acquired entity’s historical data is retained in the legacy system for reference, but all new transactions flow through the parent’s ERP from Day 1.

The advantage is speed. One system, one process, one vendor master. The disadvantage is risk: data is lost or mistranslated during forced migration, the acquired entity’s team loses access to familiar tools overnight, and any processes that depended on the legacy system break immediately. For acquisitions where the acquired entity is small and its procurement is simple, this can work. For complex acquisitions with significant operational footprint, it creates more problems than it solves.

Approach 2: Keep the Acquired ERP Running Indefinitely

The opposite approach is to keep the acquired entity’s systems running for years. This is more common than most integration playbooks acknowledge. Companies acquired five to seven years ago are sometimes still running on their original ERP, never having been migrated to the parent’s system. For serial acquirers with 22 or more business units, full ERP consolidation is not a delayed project. It is a myth they have stopped believing in. “We are never going to be a single solution,” is how one enterprise leader described their multi-system reality.

The advantage is stability. Nothing breaks. The disadvantage is fragmentation: procurement teams toggle between systems, spend data is siloed, duplicate vendors persist indefinitely, and every new acquisition adds another system to the stack.

Why Both Approaches Need an Orchestration Layer

Whether you shut down the acquired ERP immediately or keep it running for years, procurement needs a unified view across whatever systems exist. The shut-down approach creates a data translation problem (migrated records need normalization). The keep-running approach creates a data federation problem (multiple live systems need coordination). An orchestration platform solves both.

PE-owned companies undergoing divestitures face a third scenario: carving out a business unit that needs its own procurement infrastructure fast. An orchestration platform can launch procurement for a carved-out entity in as little as two weeks, compared to months for an ERP migration. This speed matters when the transaction timeline is measured in weeks, not quarters.

Opstream connects to 120+ enterprise systems including SAP, Oracle, NetSuite, Workday and Microsoft Dynamics. For organizations running multiple ERPs post-acquisition, these integration capabilities mean procurement unification starts immediately, regardless of which ERP combination exists in the stack. Organizations looking to unify indirect and direct procurement across acquired entities find this approach particularly effective because it works across every procurement category: services, hardware, consulting, facilities and software.