Reconciling SAP Licensing After a Merger

Reconciling SAP licensing after a merger is one of the most commercially loaded workstreams a buyer inherits, because SAP licensing is measured on named users, package metrics, and indirect or digital access that consolidation routinely disturbs. When two companies combine, their SAP estates rarely line up: user classifications drift, duplicate user records multiply across systems, and the connections between SAP and the rest of the application landscape change in ways that can expand the digital access footprint. Reconciling SAP licensing after a merger means measuring the combined position the way SAP measures it, quantifying the gap against entitlement, and resolving it on the buyer terms rather than waiting for an audit to fix the number for you. Inherited SAP exposure is usually latent and unquantified in standard due diligence, and it tends to surface as an audit once the new owner is known.

This guide explains how to reconcile a merged SAP estate and keep the measurement in your hands. It is a core workstream in post close license reconciliation and runs in parallel with the equivalent discipline for the other major publishers.

Reconciling SAP licensing after a merger: the metrics that bite

SAP licenses on a structure that punishes an estate that changes shape. Named user licensing assigns every user a type, from professional through to limited and self service, and the price gap between types is wide. After a merger the combined organisation often carries the same person across two systems, classifies the same role differently in each, and keeps leavers active long after they have gone. Package licensing measures consumption against metrics such as orders, contracts, or revenue, and those volumes change the moment two businesses are run as one. The reconciliation reads each agreement literally and counts the combined deployment to SAP exact definitions, not to a comfortable approximation, because SAP will do exactly that when it measures.

The same precision is needed for the other large publishers, and the disciplines overlap. Reconciling Oracle after a merger raises parallel issues of metric and counting logic, which is why this connects to reconciling Oracle licensing after a merger. The common thread is that publisher counting logic, not intuition, governs the exposure.

Indirect and digital access, the largest flashpoint

Indirect or digital access is where SAP reconciliation most often goes wrong. When a non SAP system, a custom application, a bot, or a third party platform reads or writes SAP data, SAP can treat that as licensable access even though no person logs in. A merger multiplies these connections, because the buyer integrates two application landscapes and builds new interfaces between them. SAP digital access model prices certain document types created through these connections, so an integration designed for engineering reasons alone can expand the licensable footprint sharply. The reconciliation maps every interface into and out of SAP across the merged estate and quantifies the document volume under SAP own model, so the buyer sees the exposure before integrating systems rather than after.

Managing it means making integration decisions with the licensing consequence in view. Re routing an interface, batching documents, or licensing digital access deliberately are all levers, but each has to be assessed before the landscapes are wired together. A connection made without that assessment can move the SAP position by an amount that dwarfs the engineering cost of building it.

Measuring before SAP does

The principle that governs SAP reconciliation is to measure the combined position before SAP measures it. That means reproducing SAP counting logic across the merged estate, deduplicating and reclassifying users, mapping every indirect connection, and quantifying the shortfall privately. A buyer that holds that number controls what happens next. A buyer that waits for an audit notice enters the conversation with SAP holding the measurement and the timetable. Quantifying the gap early is the same discipline as fixing under licensing before a publisher finds it, applied to a publisher with a sophisticated measurement engine of its own. The measured position depends in turn on a complete inventory, which is the work of building the combined entity license position.

The public record shows how large inherited SAP exposure can be. SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million over disputed and inherited licensing, as reported in coverage of those cases as of 2026. Those figures are a reminder that SAP indirect access and inherited terms are not theoretical, and that the time to measure is before the publisher does.

Resolving the position on the buyer terms

Once the exposure is quantified, the buyer chooses the resolution. The options include re classifying users to the type they actually need, deduplicating records across systems, re routing or re licensing indirect connections, converting to a digital access model where it is cheaper, or folding a correction into a broader negotiation that uses the combined entity larger footprint as leverage. SAP audits and conversions are commercial events as much as compliance ones, so a buyer that approaches SAP with a measured position and a credible plan negotiates very differently from one responding to an audit notice. The buyer that controls the measurement controls the timing, and the timing is most of the price. The deeper consolidation work this connects to is set out in how entity consolidation triggers license breaches.

Common reconciliation errors to avoid

Three errors recur when a buyer reconciles SAP after a merger. The first is treating the SAP user count as a headcount problem rather than a classification problem. Reducing the number of users matters far less than ensuring each remaining user holds the correct, and usually cheaper, license type for what they actually do. The second is integrating systems first and counting indirect access later, which bakes in a digital access footprint that is expensive to unwind once interfaces are live. The third is accepting the seller historical SAP measurement at face value. A position the seller never reconciled is not a baseline, it is an unmeasured liability, and the buyer inherits it. The reconciliation rebuilds the position from deployment and entitlement rather than trusting a number nobody has tested against SAP own logic.

Avoiding these errors is mostly a matter of sequence. Measure to SAP logic before integrating, classify before counting, and trust the rebuilt position over the inherited one. The same sequencing discipline runs through every workstream in the cluster, from inventory to governance.

Why an independent advisor reconciles SAP

Reconciling SAP puts a buyer against a publisher with a precise measurement model and a strong commercial incentive to find a shortfall, particularly around indirect access. An independent, buyer side advisor reproduces SAP counting logic across the merged estate, quantifies the exposure before a notice arrives, and frames the resolution on the buyer terms with no affiliation to SAP or any reseller. That independence is what keeps an SAP reconciliation a controlled decision rather than an audit the buyer enters from behind.

A worked sequence for the merged SAP estate

The reconciliation runs in a deliberate order because each step depends on the one before it. The buyer first assembles a complete inventory of both SAP agreements, the named user tables, the package metrics, and the interface catalogue, which is the inventory work set out in building the combined entity license position. Only with that inventory in hand can the team deduplicate users across both systems, because a name that appears in two user tables has to be resolved to one person before any classification is meaningful. Reclassification follows deduplication, since there is no value in assigning a license type to a record that should not exist. Indirect access mapping then sits on top of a clean user picture, because the document counts that drive the digital access model depend on knowing which connections are live and which belong to retired systems.

Timing matters as much as sequence. Many merged estates face an SAP S/4HANA conversion within the same window as the integration, and the conversion is itself a commercial event where SAP reprices the relationship. A buyer that arrives at that conversation with the merged position already measured negotiates the conversion and any indirect access correction together, rather than letting SAP set the terms of each in isolation. The overlap with other publishers running their own consolidation is handled in reconciling overlapping software agreements, so the SAP workstream stays coordinated with the rest of the estate rather than running on its own clock.

Common mistakes buyers make with SAP after a deal

The most expensive mistake is treating SAP licensing as an IT housekeeping task rather than a commercial exposure. Teams that wait for the systems to be integrated before measuring give SAP the first move, and the indirect access footprint has usually grown before anyone counts it. A second mistake is deduplicating users on identity alone, without checking the license type each duplicate holds, so the count falls but the value does not, since the surviving record may keep the more expensive classification. A third is assuming the seller declarations of the SAP position are complete, when inherited terms and undocumented interfaces are exactly the things that do not appear in a data room.

Avoiding these errors is a matter of discipline and timing. The buyer measures early, counts users by type rather than by name alone, validates the inherited position independently rather than accepting it, and treats every integration decision as a licensing decision until proven otherwise. That discipline is what turns an inherited SAP estate from a latent audit into a controlled negotiation.