Post Close License Reconciliation

Reconciling SaaS Subscriptions Across Two Companies

Reconciling SaaS subscriptions across two companies is often the fastest place to recover real money after a merger, because subscription waste hides in plain sight and compounds every month.

Reconciling SaaS subscriptions across two companies is often the fastest place to recover real money after a merger, because subscription spend hides in plain sight. Each company arrived at close with its own stack of cloud applications, bought on its own cards and renewed on its own dates, and the combined entity now pays for both. Reconciling SaaS subscriptions across two companies means finding every application both sides run, identifying the duplicate apps, dormant seats, and overlapping renewals, and consolidating onto the better agreement before the next renewal locks the waste in for another year. Unlike perpetual licenses, SaaS waste compounds monthly, so the cost of waiting is measured on the calendar.

This guide explains how to reconcile a merged SaaS estate. It is a core workstream in post close license reconciliation and feeds directly into the savings the combined entity can capture once the duplication is removed.

Reconciling SaaS subscriptions across two companies: finding the full estate

The first challenge is simply seeing the whole estate, because SaaS is bought outside the traditional procurement path more often than any other category. Departments sign up directly, charges land on expense cards, and the application never appears in an asset register. The reconciliation starts by pulling spend from finance and expense systems, not just from IT, because the finance trail is the most complete record of what is actually being paid. Single sign on logs and identity systems then reveal which applications are actually used and by whom, which separates a live subscription from one that renews unnoticed.

Once the estate is visible, the duplicates emerge. Two companies almost always run competing tools for the same job: two collaboration suites, two CRM platforms, two project trackers, two security tools. Each duplicate is a consolidation decision and a recurring saving. This is the SaaS form of the broader work covered in reconciling overlapping software agreements, where the choice of which agreement to keep rests on full economics rather than headline price.

Where SaaS waste concentrates after a mergerBar chart showing the relative size of recoverable SaaS spend across duplicate applications, dormant seats, overlapping renewals, over provisioned tiers and unused add ons after a merger.Where SaaS waste concentrates after a merger85%Duplicate apps70%Dormant seats65%Overlap renewals50%Over tiered40%Unused add ons

Dormant seats and over provisioned tiers

Beyond duplicate applications, the largest single source of SaaS waste is seats that are paid for but not used. After a merger, headcount changes, leavers are slow to be deprovisioned, and seat counts set before the deal no longer match the people on the system. Reconciling actual active users against contracted seats almost always reveals a block of dormant licenses the combined entity can shed at renewal. The same is true of pricing tiers and add on modules bought for a feature one company needed and the other does not. The reconciliation tests each subscription against real usage, not against the number on the order form.

Timing is the constraint that makes this urgent. A SaaS contract that auto renews carries its dormant seats and over provisioned tiers into the next term, so the saving is only available in the window before renewal. Mapping every renewal date is therefore part of the reconciliation, not an afterthought, because a saving identified after the renewal has passed is a saving deferred a full year.

SaaS reconciliation findings and how to act
FindingHow to confirmAction before renewal
Duplicate applicationsTwo tools, one capabilityChoose one on full economics, migrate users
Dormant seatsActive users below contracted seatsReduce seat count at renewal
Over provisioned tierPremium features unusedStep down to the right tier
Unused add on modulesNo usage in either companyDrop the add on at renewal
Overlapping renewalsTwo contracts, different datesAlign or stagger to keep leverage

Key takeaways

  • SaaS waste compounds monthly, so the cost of delaying reconciliation is measured on the calendar.
  • Finance and expense data, not the asset register, is the most complete record of what is actually paid.
  • Duplicate applications, dormant seats, and over provisioned tiers are the three largest sources of recoverable spend.
  • Every saving is gated by a renewal date, so mapping renewals is part of the reconciliation.
  • Reconciled SaaS waste becomes a recurring saving the combined entity keeps every year.

Consolidating without breaking coverage

Removing duplication has to be sequenced so the business never loses a tool it relies on. Cancelling a subscription before users have migrated to the retained platform creates an outage, and cancelling before a notice period has been met can leave the combined entity paying anyway. The disciplined approach migrates first and cancels second, with every renewal and notice date mapped so coverage never lapses. The savings only land once the redundant subscription actually ends, which connects this work to deduplicating software spend after an acquisition, where the recovered cost is tracked and banked.

Cloud entitlements that sit alongside SaaS need the same treatment, because a merged entity often holds overlapping cloud platform commitments as well as application subscriptions. Reconciling them together avoids leaving value on the table, which is why this connects to reconciling cloud entitlements across entities.

Holding leverage at the SaaS renewal

A combined entity that has reconciled its SaaS estate walks into each renewal with a genuine alternative, because it can credibly consolidate onto either platform it holds. That optionality is worth real money, since a vendor that knows its customer can move negotiates differently from one that assumes lock in. The buyer that maps its duplicates and renewals before the conversation arrives sets the terms rather than reacting to them. The reconciliation is what turns scattered subscriptions into a single, leveraged negotiating position.

Recommendations for buyers

  1. Pull SaaS spend from finance and expense systems first, since shadow purchases never reach the asset register.
  2. Use single sign on and identity data to separate active subscriptions from dormant ones.
  3. Identify duplicate applications and choose which to keep on full economics, not headline price.
  4. Reconcile contracted seats against active users and shed dormant seats at the next renewal.
  5. Map every renewal and notice date so savings are captured in the window before auto renewal.
  6. Migrate users before cancelling any subscription so coverage never lapses.

Why an independent advisor reconciles the SaaS estate

Reconciling a merged SaaS estate puts a buyer across the table from vendors who would rather keep both subscriptions running. An independent, buyer side advisor with no affiliation to any vendor or reseller finds the duplication, tests every seat against real usage, and sequences the consolidation so the combined entity captures the saving without losing a tool the business needs. That independence is what turns scattered subscription spend into recurring recovered value.

Independent and buyer side. We act only for the acquirer. We hold no affiliation with any software publisher or reseller and are paid solely by you. This page is commercial and licensing guidance, not legal advice. Confirm any contractual interpretation with your own counsel.

Frequently asked questions

What does reconciling SaaS subscriptions across two companies mean?

It means finding every cloud application both companies run, identifying duplicate apps, dormant seats, and overlapping renewals, and consolidating onto the better agreement before the next renewal locks the waste in. The aim is to stop the combined entity paying twice for the same capability.

Where is SaaS spend usually hidden?

Outside the traditional procurement path. Departments sign up directly and charges land on expense cards, so the application never reaches the asset register. Finance and expense data is the most complete record of what is actually being paid.

What is the biggest source of SaaS waste after a merger?

Duplicate applications and dormant seats. Two companies almost always run competing tools for the same job, and seat counts set before the deal rarely match the people actually on the system afterward.

Why does timing matter so much with SaaS?

Because a SaaS contract that auto renews carries its dormant seats and over provisioned tiers into the next term. The saving is only available in the window before renewal, so mapping every renewal date is part of the reconciliation.

How do you consolidate without breaking coverage?

Migrate users to the retained platform first, then cancel the redundant subscription once notice periods are met. Cancelling before migration creates an outage, and cancelling before notice leaves the entity paying anyway.

How much can SaaS reconciliation save?

It varies by estate, but duplicate applications, dormant seats, and over provisioned tiers together typically yield a meaningful recurring saving because SaaS waste compounds every month it is left in place.

Reconcile the combined estate before a publisher does.

We build the combined entity license position, find the breaches consolidation creates, and fix them on your terms before an audit lands.

Request a confidential reconciliation