Temporary License Bridging for SAP Access During M&A Transitions

Why M&A Transactions Expose SAP Licence Gaps

SAP licence agreements are written for stable organisational structures. They define named users, system landscapes, and company codes as they exist at signing. A merger, acquisition, or divestiture disrupts every one of those reference points simultaneously. Acquiring entities inherit the target's licence obligations but rarely inherit a complete picture of what those obligations are. Divesting entities must continue operating their SAP landscape for months under Transitional Service Agreements (TSAs) while legally separated from their former parent's contract.

The result is a window of elevated compliance risk that SAP audit teams know how to exploit. SAP's fiscal year ends on 31 December, which means year-end audit pressure aligns with Q4 deal closings — one of the busiest periods for corporate transactions. Organisations that fail to address the licence position before day one of a deal are almost invariably in a worse position than those that negotiate bridge arrangements in advance.

In our experience defending over 80 indirect access and digital access disputes, M&A transitions consistently produce the largest unexpected licence claims because they combine three separate risk vectors at once: named user misclassification, DDLC metric underestimation, and TSA system access that nobody remembered to licence.

Temporary Use Licences: What They Cover and What They Don't

SAP's standard mechanism for bridging licence continuity during M&A transactions is the Temporary Use Licence (TUL). Understanding precisely what a TUL covers is essential before relying on one as your compliance backstop.

What TULs Typically Cover

A TUL grants named user access to defined SAP systems for a specified period — typically six to eighteen months — for entities that are in transition. In a divestiture context, the divested entity retains access to the parent's SAP environment under the TUL while it builds or migrates to its own system. In an acquisition context, the acquired entity's users may be brought onto the acquirer's contract under TUL provisions while a full licence reconciliation is conducted.

SAP prices TULs at approximately 10 to 20 percent of the divested or acquired unit's licence value for a twelve-month period. This is the list rate. Organisations that commit to a RISE with SAP subscription or a significant new licence purchase as part of the same transaction have successfully negotiated TUL fees as low as 5 to 8 percent — a meaningful saving on a multimillion-pound baseline.

What TULs Do Not Cover

This is the critical gap that produces audit claims. A TUL typically covers named user access and does not automatically extend to digital access or indirect use. If the transitioning entity's systems send data to or receive data from the host's SAP instance — for example, a shared procurement platform, an integrated HR system, or an automated ERP-to-ERP interface — those interactions may trigger separate digital access licensing requirements.

SAP measures indirect access under the Digital Document Licence Count (DDLC) metric. DDLC counts the number of certain document types created in SAP by external systems or automated processes rather than by named users logging in directly. When a non-SAP application creates a sales order, a purchase order, an invoice, a financial posting, or any of the nine recognised digital document types, each creation generates a DDLC count that must be covered by a separate digital access licence.

During an M&A transition, cross-entity system integrations are common and often poorly documented. A shared warehouse management system, a group-level treasury platform, or a common HR platform feeding data into SAP will all generate DDLC events that the TUL does not address. SAP auditors specifically target these integration points because they know the compliance gap exists.

The DDLC Metric Explained

The DDLC metric was introduced by SAP as part of its Digital Access model in 2018, replacing the older and more aggressive indirect access licensing approach that had produced multi-hundred-million-pound claims against large enterprises. Understanding how DDLC works is essential for any organisation managing SAP access during a corporate transaction.

Under DDLC, SAP charges are based on nine specific document types when those documents are created in SAP by an external, non-SAP system. The nine document categories are: sales documents, purchase documents, invoice documents, financial documents, material documents, service documents, plant maintenance documents, quality management documents, and project system documents. Each category has further subcategories defined in SAP's Digital Access price list.

Critically, DDLC counts creation events only. Reading, updating, or deleting an existing document does not generate a further DDLC count. And if one external event triggers a chain of SAP document creations — for example, an inbound order that creates a sales order, which then triggers a delivery and an invoice — only the originating document in the chain counts, not every downstream document in the process flow.

Despite this relatively contained definition, organisations routinely underestimate DDLC exposure during M&A because they have never counted the number of SAP documents created by external systems. When SAP's audit team runs its standard interface and document counting scripts on an M&A-affected landscape, the numbers can be surprising. A mid-sized manufacturing operation with typical ERP integrations may generate several hundred thousand DDLC events per year across its external system connections.

How SAP Constructs DDLC Audit Claims

SAP's approach to constructing an indirect access or digital access audit claim follows a consistent pattern. First, SAP obtains consent to run a Technical Measurement Tool (TMT) or equivalent script on the customer's system. The TMT queries SAP's system log tables to identify interface connections, the volume of documents created through those connections, and the document types involved. SAP then maps the document counts to its digital access price list and calculates the cumulative licence shortfall.

In an M&A context, SAP may argue that the transition period itself — during which the acquired or divested entity was operating on the parent's contract without digital access coverage — constitutes a retroactive licence shortfall. The claim is not limited to the future period; it can reach back to when the system integration was first established, which in practice may predate the transaction itself.

Defending these claims requires a combination of technical analysis (demonstrating which document types were created and in what volumes), legal interpretation (arguing that TSA provisions provide coverage for the transition period), and commercial negotiation (trading the DDLC claim against a forward-looking RISE commitment or new licence purchase).

S/4HANA Migration and Baseline Recalibration

Any M&A transaction that intersects with an S/4HANA migration programme adds a further layer of complexity. S/4HANA migration changes the licence baseline in ways that can work either for or against the customer, depending on how the transition is structured.

Under legacy SAP ECC contracts, named users were licensed under a classification hierarchy (Professional, Limited Professional, Employee Self-Service, and so on) with complex rules governing what each user type could do. S/4HANA introduces the Full User Equivalent (FUE) metric, which simplifies the classification but can inflate the total licence cost if the migration is not carefully managed. An ECC estate with a large proportion of Employee Self-Service users may look materially more expensive when recalculated as FUEs because SAP's FUE conversion ratios do not always favour the customer.

In a divestiture scenario, the divested entity will typically need to establish a new SAP contract when it exits the parent's licence umbrella. If the parent is on ECC and the divestiture timeline overlaps with SAP's end-of-mainstream-maintenance for ECC (currently extended to 2027), the divested entity faces a choice: sign a new ECC contract (time-limited and potentially expensive), move directly to RISE with SAP (locking in cloud subscription costs from day one), or negotiate a hybrid arrangement that bridges ECC access while a migration strategy is developed.

This is precisely the moment when independent adviser involvement delivers the greatest return. SAP's sales team will propose a RISE contract that maximises future revenue. A buyer-side adviser will identify the optimal bridge arrangement, negotiate the TUL at the lowest defensible rate, and structure a forward RISE or S/4HANA commitment that reflects actual need rather than SAP's preferred deal size.

Negotiating SAP Grace Periods and Written Protections

One of the most valuable protections an organisation can secure during M&A is a written grace period agreement with SAP. This is an agreement — ideally embedded in the main transaction documentation or in a side letter from SAP — that specifies a defined window during which cross-system integrations will not trigger audit findings or additional licence fees, regardless of DDLC events.

SAP does not offer grace periods as a standard product. They must be negotiated, and SAP's willingness to grant them is typically contingent on a credible forward commitment — either a RISE migration plan with a signed letter of intent, or a confirmed new licence purchase that compensates SAP for the transitional period. The leverage point is SAP's fiscal year end on 31 December: deals that close before year end allow SAP to book revenue in the current fiscal year, which typically increases SAP's flexibility on adjacent terms including grace period provisions.

Key Terms to Negotiate in a Bridge Arrangement

A well-negotiated SAP bridge arrangement for an M&A transition should include the following protections:

• Written TUL documentation: The TUL should be executed as a formal amendment to the main licence agreement, not left as a verbal understanding with the account team. Verbal commitments from SAP account executives have no contractual standing.
• Explicit DDLC coverage: The TUL should either explicitly extend to digital access document counts generated during the bridge period, or a separate digital access licence should be procured. The coverage gap between TUL (named users) and DDLC (automated integrations) must be closed in writing.
• Audit freeze provision: Request a contractual commitment from SAP that no audit will be initiated against the transitioning entity for a defined period (typically twelve to eighteen months from transaction close).
• Price cap on renewal: If the bridge arrangement may extend beyond its initial term, negotiate a cap on the rate at which SAP can increase the TUL fee on renewal. SAP annual support is approximately 22% of net licence value — a meaningful number when extrapolated over a multi-year transition.
• Continuity of existing contract terms: Ensure that the TUL does not inadvertently reset the clock on any perpetual licence rights or favourable contract terms that the divested entity would otherwise retain.

RISE with SAP and What It Includes in M&A Contexts

Organisations moving to RISE with SAP as part of an M&A transition should understand precisely what the RISE subscription includes and what it does not, because SAP's sales materials consistently overstate the scope of inclusion.

RISE with SAP includes S/4HANA Cloud Private Edition hosted in SAP's chosen hyperscaler environment, SAP Business Technology Platform (BTP) credits at a defined baseline, SAP Signavio (process intelligence tooling), SAP Business Network Starter Pack, and access to SAP's premium engagement services. What RISE does not include: industry-specific add-ons, SAP SuccessFactors, SAP Ariba, SAP Concur, SAP Customer Experience products, third-party application integration beyond the BTP baseline, or any legacy ECC licences that may need to run in parallel during a phased migration.

In an M&A transition, the acquired entity may be running SuccessFactors or Ariba on separate contracts that were not included in the parent's RISE scope. The divested entity will need to negotiate these products separately. SAP's tendency is to present RISE as an all-inclusive platform — but the financial reality requires line-by-line verification of what is and is not covered in the specific contract being executed.

BTP credits within RISE deserve particular scrutiny. The baseline BTP allocation included in RISE is typically insufficient for complex integration workloads, and M&A transitions commonly involve exactly the kind of integration-heavy scenarios that exhaust BTP credits rapidly. Organisations should model their BTP consumption requirements before signing and negotiate an appropriate credit baseline rather than accepting the default allocation.

Practical Steps Before Day One

The window between deal signing and transaction close — typically sixty to ninety days — is the most important period for SAP licence management. Organisations that use this window effectively arrive at day one with a documented licence position, a negotiated bridge arrangement, and a clear understanding of their DDLC exposure. Those that do not use the window typically spend the following twelve to eighteen months unwinding compliance problems that could have been avoided.

Pre-Close Licence Audit Checklist

Before transaction close, the following steps should be completed:

• Obtain and review the target entity's current SAP licence agreement, including all amendments and order forms dating back to the most recent system landscape change.
• Identify all system integrations connecting non-SAP applications to the SAP environment and classify them by document type for DDLC exposure assessment.
• Run a named user analysis using SAP's licence compliance tools or a third-party measurement solution to establish the true named user position before any TUL negotiation.
• Request SAP's disclosure of any open audit or measurement findings against the target entity — these should be treated as a deal-level risk and reflected in the transaction price if material.
• Identify any S/4HANA migration commitments already made by the target entity that will need to be honoured, novated, or renegotiated as part of the transaction.
• Engage SAP's account team early — not to accept their proposed bridge arrangement, but to establish the relationship and begin the negotiation process before time pressure limits your options.

How Redress Compliance Supports M&A SAP Transitions

Redress Compliance operates exclusively on the buyer side. We have managed SAP licence positions through more than 80 indirect access and digital access disputes, and have supported M&A transactions ranging from carve-outs of single business units to cross-border acquisitions involving multiple SAP system landscapes.

Our involvement in an M&A context typically begins at the due diligence phase, where we assess the target's SAP licence position and quantify the DDLC exposure inherent in their integration landscape. We work through signing and close to negotiate TUL arrangements, grace period provisions, and forward RISE or S/4HANA commitments that are proportionate to the entity's actual requirements. And we continue post-close to manage the transition programme, defend any audit claims that arise, and ensure that the acquired or divested entity lands on the right licence model at the right cost.

If your organisation is approaching an M&A transaction involving SAP — or if you have recently completed one and are now managing the licence consequences — contact us for a confidential, no-obligation assessment of your position.