Electrolux Chooses Redress Compliance for Advisory Services in Mergers and Acquisitions

Why Electrolux Engaged Independent Licensing Advisory for M&A

Electrolux completed more than 50 acquisitions over three decades — each one creating software licence exposure that traditional due diligence processes routinely missed.

The challenge that prompted Electrolux to engage Redress Compliance was a recognition that software licensing risk — specifically, the risk of acquiring undisclosed licence liabilities that trigger audit exposure or renegotiation demands post-close — was not being systematically assessed as part of the M&A due diligence process. This is not unique to Electrolux. It is a gap that exists across the majority of M&A transactions globally, because the teams conducting financial and legal due diligence typically lack the specialist enterprise software licensing expertise required to identify and quantify licensing risk at the depth that vendors can and will exploit post-transaction.

Enterprise software vendors — Oracle, SAP, IBM, and others — have well-documented practices of conducting licence audits shortly after M&A transactions close, specifically targeting the licence compliance implications of the change of control event, the integration of acquired entities' technology estates, and the use of the acquired entity's software licences in the combined enterprise. The period immediately following M&A closing, when IT integration teams are at their most stretched, is the period when vendor audit teams are most active.

The Scope of the Engagement

Redress Compliance was engaged to deliver a structured licensing due diligence assessment covering the enterprise software estate of the target entity, with specific focus on the vendors and contract terms most likely to create post-transaction compliance exposure. The engagement was structured in two phases: a pre-close due diligence assessment to identify licence risks and inform deal valuation, and a post-close integration advisory to support Electrolux's IT integration teams in managing the licence implications of bringing the acquired entity's technology environment into the Electrolux estate.

Oracle Licence Risk Assessment

Oracle represents the most frequently material licence risk in M&A transactions because of three structural features of Oracle's licensing model. First, Oracle's deployment-based licensing — particularly for its database products — creates risk whenever acquired entity deployments are migrated to new infrastructure or consolidated with the acquirer's existing Oracle environment. Each migration and consolidation event can trigger a change in the licensed deployment context that Oracle's audit teams interpret as requiring additional licensing or certification.

Second, Oracle's virtualisation rules — specifically the restrictions on running Oracle licences in virtual environments without complying with Oracle's specific hard partitioning or full soft partitioning requirements — create compliance exposure whenever acquired entity Oracle deployments run on VMware, cloud infrastructure, or other virtualised environments that Oracle does not recognise as compliant partitioning. Oracle audits following M&A transactions routinely surface virtualisation-related licence gaps that were not visible in the pre-transaction due diligence.

Third, Oracle's network use rules mean that any Oracle software accessible to a user through the network must be licensed for that user. When an acquired entity's Oracle applications are integrated into the acquirer's network environment, the accessible user population may expand significantly, potentially triggering licence requirements for users in the acquirer's organisation who can reach the Oracle environment.

The assessment identified specific Oracle licence risk categories within the target entity's deployment, quantified the potential exposure range, and recommended contractual protections to negotiate in the transaction documentation — specifically, representations and warranties from the seller regarding Oracle compliance status, and provisions allocating Oracle audit liability for pre-close compliance periods.

SAP Contract and Licence Analysis

SAP licensing in M&A transactions creates risk through two primary mechanisms. The first is indirect access — the use of SAP data or functionality through non-SAP applications, custom interfaces, or third-party integrations that SAP may characterise as requiring additional licensing for the users or digital access events that touch the SAP system. SAP's enforcement of indirect access rules has been a major source of post-M&A licence disputes, particularly where the acquired entity has developed custom integration architectures that were not designed with SAP's indirect access rules in mind.

The second is the classification of SAP users. SAP's user-based licence model differentiates between licence types — Full User, Limited Professional User, Employee Self-Service, and others — based on the tasks each user performs. Acquisitions frequently result in expanded user populations accessing SAP systems under licence types that do not cover their actual usage, creating compliance gaps that SAP's audit teams identify during the post-transaction contract review that SAP typically conducts within 12 to 18 months of an M&A transaction.

The SAP assessment for Electrolux included analysis of the target entity's named user licence allocation against actual system access patterns, identification of potential indirect access risk from third-party integrations, and review of the SAP contract terms governing change of control and licence assignment provisions.

Microsoft Estate Integration Planning

Microsoft licensing in M&A transactions is primarily governed by change of control provisions in the Enterprise Agreement and by Microsoft's tenant consolidation rules for Microsoft 365 and Dynamics 365. When an acquired entity holds its own Microsoft EA or M365 tenancy, the integration process — merging directories, consolidating tenants, migrating users to the acquirer's Microsoft environment — must be planned carefully against Microsoft's licence assignment and reassignment rules to avoid creating periods of unlicensed use or double-payment for users transitioning between environments.

The Microsoft assessment covered the target entity's M365 licence position, EA terms and remaining commitment periods, Dynamics 365 deployment scope and licence types, and the integration sequence required to consolidate the target's Microsoft environment into Electrolux's existing Microsoft estate without triggering licence compliance gaps during the transition period.

The Value of Independent Licensing Advisory in M&A

The fundamental value proposition of independent licensing advisory in M&A is that the organisations best positioned to identify and quantify software licence risk — the vendors themselves — have a financial incentive to exploit that risk post-close rather than disclose it pre-close. Oracle's audit business, SAP's licence compliance team, and IBM's contract management organisation are sophisticated commercial operations with detailed records of how M&A transactions affect licence compliance positions. These teams are not hired by buyers to protect buyer interests; they are hired by vendors to optimise vendor revenue.

An independent adviser who is genuinely buyer-side — with no vendor affiliation, no reseller relationship, and no financial interest in any outcome other than the client's — provides an objective assessment of licence risk that vendor-aligned consultants, implementation partners, and software resellers cannot. Redress Compliance's business model is built entirely on buyer-side advisory. We do not sell software licences, we do not receive vendor referral fees, and we do not hold channel partner relationships with the vendors we advise on. This independence is the structural prerequisite for genuinely objective licensing due diligence.

What M&A Licensing Due Diligence Should Cover

Based on our experience across more than 150 M&A licensing engagements, the following areas represent the most common and most material sources of enterprise software licence risk in M&A transactions. Any due diligence process that does not address each of these areas is leaving identifiable risk on the table.

Change of Control Provisions

Most enterprise software agreements contain change of control clauses that give the vendor specific rights when a contracting entity is acquired, merged, or undergoes significant ownership change. These rights vary by vendor and contract but commonly include the right to terminate the agreement, the right to renegotiate terms, the right to require assignment of the agreement to the acquirer, and the right to conduct a licence compliance audit. Understanding what change of control rights each major vendor holds in the target entity's contracts is essential for assessing post-close vendor negotiation exposure.

Deployment Environment Compliance

The target entity's software deployments must be validated against the licence terms governing those deployments — not against the contracts alone, but against the vendor's current licence policies, which may differ from the contracts' explicit language. Oracle's Technology Licence Policy, IBM's licensing rules for virtualised environments, and SAP's indirect access policies are all sources of licence risk that can exist independent of what the contracts say, because vendor enforcement positions evolve and audit teams apply current policies to historical deployments.

Integration Architecture Risk

The planned integration architecture for merging the acquired entity's systems with the acquirer's environment must be assessed for licence implications before integration begins. Migrating the acquired entity's Oracle database to the acquirer's VMware infrastructure, consolidating SAP instances, or merging Microsoft tenants all have licence implications that, if unaddressed, can create material compliance exposure during the integration period when vendor audit activity is at its highest.

Why Electrolux's Approach Sets the Standard

Electrolux's decision to engage independent licensing advisory as a formal component of its M&A due diligence process reflects a level of software licensing sophistication that is still relatively rare among global enterprises. The more common approach — relying on legal counsel to review contract terms and on internal IT teams to assess deployment configurations — consistently misses the specialist licensing analysis required to identify and quantify the risks that Oracle, SAP, IBM, and Microsoft audit teams are trained to find.

The consequence of that gap is documented across dozens of post-M&A licensing disputes that have become public: multi-million dollar audit settlements, forced renegotiations at unfavourable terms, and integration delays caused by vendor commercial disputes. The cost of independent licensing due diligence is a small fraction of the exposure it prevents.

For enterprises planning M&A activity involving targets with significant enterprise software estates, Electrolux's approach provides the operational template: engage independent specialist advisory early in the due diligence process, scope the assessment to cover all major vendor relationships in the target, use the findings to inform deal valuation and contract representations, and plan the post-close integration with the vendor licence implications mapped before execution begins.