When companies merge, acquire, or divest, SAP systems rarely move as fast as the deal. Employees of one legal entity end up using another’s SAP environment — creating immediate compliance exposure. Temporary licence bridging provides the compliant, structured framework CIOs need to maintain business continuity without triggering audit findings, back-dated true-ups, or multi-million-dollar penalties.
In mergers, acquisitions, and divestitures, IT systems integrate far more slowly than the business transaction itself. A newly acquired subsidiary may rely on the acquirer’s SAP ERP to process orders from Day 1. A spun-off entity may need to continue using the parent’s SAP system for 6–18 months until its own environment is operational. In both cases, employees of one legal entity are using SAP software licensed to a different legal entity.
SAP’s standard contracts include strict non-transferability clauses. Licences are tied to specific legal entities and cannot be shared with, or transferred to, third parties without SAP’s written consent. When a divestiture or acquisition creates a new legal entity boundary, every user crossing that boundary is technically unlicensed — regardless of whether the underlying system, data, or processes remain unchanged.
SAP actively monitors M&A events and frequently triggers audits following corporate restructuring. The risk is not theoretical: enterprises regularly face multi-million-dollar true-up demands when SAP discovers that transitional access was provided without proper licensing arrangements.
“Every M&A deal involving SAP creates a licensing gap between the legal close and the IT separation. The enterprises that avoid audit exposure are the ones that plan the licence bridge before the deal closes, not after.”
For comprehensive guidance on managing SAP licensing throughout corporate transactions, see Managing SAP Licensing During Mergers, Acquisitions & Divestitures.
Understanding SAP’s specific contractual constraints around entity changes is essential before designing any bridging arrangement.
If employees of Company A log into Company B’s SAP system without a formal agreement, both parties are non-compliant. The host company is providing unlicensed access, and the accessing company is using SAP without a valid licence. SAP will pursue both.
SAP can — and does — demand retroactive licence purchases for the entire period of unlicensed access. A 12-month period with 200 unlicensed users can easily generate a $1–3M true-up demand at list price, plus back-dated maintenance at 22%.
Without proper planning, the parent retains (and pays maintenance on) licences it no longer needs, while the separated entity must purchase a completely new SAP estate at current prices. The combined cost is substantially higher than a planned transition.
For specific guidance on divestiture licensing strategies, see Divesting a Business Unit Running SAP.
The most common and well-established bridging mechanism is a Transitional Service Agreement that includes SAP’s formal consent for the transitional entity to continue using the host company’s SAP system.
The parent (or seller) agrees to continue providing SAP system access to the separated entity for a defined period (typically 6–18 months). SAP issues a Temporary Use Letter (TUL) or contract addendum authorising the arrangement.
SAP typically charges 10–20% of the divested unit’s licence value for the transition period. This is substantially cheaper than the separated entity purchasing a full new SAP estate. Fees are negotiable — especially when bundled with the long-term licensing commitment.
TSA periods are finite — typically 6, 12, or 18 months. Extensions are possible but require renegotiation with both the counterparty and SAP. Plan the permanent solution from Day 1; do not assume extensions will be granted.
Fully compliant when SAP’s written consent is in place. The TUL explicitly authorises the cross-entity access for the defined period, users, and products. This is your audit defence document.
For broader contract negotiation strategies, see SAP Contract Negotiation Playbook.
In scenarios where a TSA is impractical — for example, when the separated entity needs its own SAP instance immediately or when the seller is unwilling to provide ongoing system access — the acquiring or separated entity can purchase temporary SAP licences directly.
SAP offers short-term or “subscription-style” licence arrangements for transitional periods. These provide full SAP access for 6–24 months without the long-term commitment of a perpetual purchase. Pricing is typically per-user per-month, negotiable based on volume and strategic context.
In some M&A structures, it is possible to negotiate the transfer of existing SAP licences from the seller to the buyer as part of the transaction. SAP must consent to the transfer (it is not automatic), and SAP often uses this as an opportunity to require a contract update or upgrade commitment.
If the separated entity plans to purchase SAP long-term, negotiate a structure where the temporary licence fees are credited against the permanent purchase. This avoids paying twice — once for the bridge and once for the permanent estate. SAP will offer this to secure the long-term deal.
Redress Compliance provides independent SAP licensing advisory services — fixed-fee, no vendor affiliations. Our specialists have helped enterprises save millions through strategic licence optimization, Digital Access negotiation, and contract restructuring.
Explore SAP Advisory Services →When sharing the original SAP system is impractical or contractually prohibited, a third-party-hosted or cloud-based bridge environment provides an independent SAP instance for the transitioning entity.
An SAP-certified hosting partner runs a dedicated SAP instance for the transition. The partner provides the infrastructure, SAP licences (bundled or BYOL), and managed services. Deployment in 4–8 weeks. Ideal for 6–24 month bridge periods.
SAP’s RISE offering can serve as a bridge: the separated entity subscribes to RISE for a short term, migrates data to the RISE instance, and operates independently. If the entity plans to adopt RISE permanently, this eliminates the bridge entirely. See RISE vs GROW Comparison.
A technical carve-out creates a copy of the relevant portion of the parent’s SAP system for the separated entity. This is the most operationally seamless option but requires 8–16 weeks of implementation and a new SAP licence agreement for the carved-out instance.
Run the TSA-based bridge on the parent’s system while simultaneously building the permanent environment. The separated entity migrates users in phases. This reduces Day 1 risk while providing a structured path to independence.
For cloud vs on-premise considerations, see SAP Cloud & Hybrid Licensing Strategies and Cloud vs On-Premise Credits — Avoiding Double Payment.
The financial impact of each bridging approach varies significantly. The table below compares representative costs for a 500-user SAP environment with $5M in licence value.
| Bridging Option | Upfront Cost | Monthly Cost (est.) | 12-Month Total | Key Considerations |
|---|---|---|---|---|
| TSA with SAP TUL | $500K–$1M (TUL fee) | Included in TUL | $500K–$1M | Lowest cost; requires seller cooperation and SAP consent. Most common approach. |
| Temporary licence purchase | Varies | $80–$150/user | $480K–$900K | Entity-independent; can credit against permanent purchase. Flexible scope. |
| Partner managed cloud | $100K–$200K setup | $100–$200/user | $700K–$1.4M | Independent instance; 4–8 week deployment. Higher cost but full autonomy. |
| RISE bridge | Minimal | $150–$300/user | $900K–$1.8M | Best if RISE is the permanent target. Eliminates double migration. |
| System carve-out | $200K–$500K | $50–$100/user (hosting) | $500K–$1.1M | Most operationally seamless; longest lead time (8–16 weeks). |
| No bridging (audit risk) | $0 | $0 | $1–$5M+ (audit finding) | Appears free but creates the highest total cost. Never recommended. |
The “no bridging” option is never the cheapest. Enterprises that skip formal bridging consistently pay 3–10× more in audit findings, back-dated maintenance, and emergency licence purchases than those that plan a proper bridge. The bridge is an investment in risk avoidance, not an optional cost. Factor it into the M&A transaction budget from the earliest planning stage.
A compliant bridge requires more than a commercial agreement — it requires a documented compliance architecture that will withstand SAP’s scrutiny during any subsequent audit.
Clearly define which legal entities are involved, which entity holds the SAP licence, and which entity’s employees are accessing the system. The TUL or bridge agreement must explicitly name these entities.
Determine exactly how many users from the transitioning entity need access, and at what licence level (Professional, Functional, Productivity). Do not over-provision — every bridged user adds to the temporary licence cost.
If the transitioning entity’s systems (CRM, e-commerce, RPA) send or receive data from the host’s SAP instance, digital access licensing may apply independently of named user counts. Review and document all integration points. See SAP Digital Access Guide.
Implement user access logging that tracks which entity’s employees are using the system, what transactions they execute, and the total user count. This data is your audit defence if SAP questions the bridge arrangement.
The bridge is temporary. Define the target end date, the permanent licensing solution, and the migration path before activating the bridge. Every month of extension beyond the planned end date increases cost and complexity.
SAP’s definition of “use” is broad. Even read-only access, report viewing, and data extraction through interfaces count as licensed usage. Do not assume that because a user “only views reports” they do not require a licence during the bridge period. Map every access point, including automated integrations and batch processes that cross the entity boundary.
SAP’s licensing and sales teams are sophisticated in their approach to M&A events. Understanding their likely behaviour helps CIOs prepare and negotiate more effectively.
SAP monitors M&A announcements. When a deal involving an SAP customer is announced, SAP’s licence compliance and sales teams will proactively contact both parties. They will frame this as “helping you stay compliant” — but the commercial objective is to maximise licence revenue from the transaction.
SAP frequently initiates audits 6–18 months after M&A events. They target the period between deal close and IT separation, looking for unlicensed cross-entity access. If you have proper bridging documentation, the audit is straightforward. Without it, findings can be substantial.
SAP will use the M&A event to push both entities toward new commitments — RISE subscriptions, S/4HANA migrations, expanded user counts. Some of these may align with your plans; others are opportunistic. Evaluate each on merit and separate the bridge negotiation from the long-term commitment where possible.
For notification and communication strategies, see Managing SAP Notifications for Company Changes.
Licence bridging errors during M&A are remarkably common — and remarkably expensive. Below are the mistakes we see most frequently in our advisory practice.
| Mistake | Consequence | Prevention |
|---|---|---|
| No bridging arrangement at all | $1–5M+ audit finding; retroactive true-up at list price | Plan the bridge as part of M&A due diligence; engage SAP 60–90 days before close |
| TSA without SAP consent | TSA is valid between parties but SAP still considers use unlicensed | Always obtain SAP’s written TUL or contract addendum in addition to the inter-company TSA |
| Underestimating user counts | Bridge covers 300 users but 450 actually access the system; audit finds 150 unlicensed | Include 10–15% buffer; implement access controls; monitor actual usage weekly |
| Forgetting digital access | Automated interfaces between entities create unlicensed indirect/digital access | Map all integration points; include digital access in bridge scope |
| No exit plan | Bridge extends indefinitely; costs accumulate; SAP charges extension premiums | Define the permanent solution and migration timeline before activating the bridge |
| Stranded licences | Parent pays maintenance on licences the divested entity is using; no commercial recovery | Negotiate licence transfer or support reduction as part of the M&A agreement |
For comprehensive guidance on avoiding SAP licensing pitfalls, see Top 10 SAP Licensing Pitfalls for CIOs.
Below is the complete execution framework for planning and implementing SAP licence bridging during M&A transitions.
From the earliest deal planning stage, inventory all SAP products, user counts, licence types, and contract terms for both entities. Identify every SAP system that will be affected by the transaction. Quantify the bridging requirement.
Estimate how long the transitioning entity will need access to the other party’s SAP system. Be realistic — IT separations consistently take longer than planned. Plan for 12 months minimum; negotiate extension options for 18–24 months.
Choose from: TSA with SAP consent (most common), temporary licence purchase, partner-hosted bridge, RISE bridge, or system carve-out. Selection depends on seller cooperation, timeline, budget, and the permanent licensing strategy.
Initiate the licensing discussion with SAP’s M&A licensing team. Present your bridge plan and request the TUL or contract addendum. Do not wait until after close — every day without documentation is a day of compliance exposure.
Bundle the bridge arrangement with the separated entity’s permanent licensing commitment. This gives SAP commercial motivation to offer favourable bridge terms and gives you leverage to negotiate the permanent deal from a position of strength.
Obtain SAP’s TUL, execute the inter-company TSA (if applicable), and ensure the bridge agreement specifies: products, user counts (with buffer), entity names, start date, end date, extension terms, and fees. Legal review is non-negotiable.
Configure SAP access controls to track cross-entity usage. Log which entity’s employees access the system, how many, and what transactions they execute. This monitoring data is your audit defence documentation.
Start building the permanent SAP environment (new instance, RISE subscription, or alternative ERP) from Day 1 of the bridge. Do not wait until the bridge is expiring. The bridge buys time; use it.
Transfer users from the bridge system to the permanent environment in planned waves. Validate data integrity, process continuity, and user access at each phase. Reduce bridge user counts (and costs) as each wave migrates.
When all users have migrated, formally terminate the bridge agreement, deactivate cross-entity access, and confirm with SAP that the transitional arrangement is closed. Retain all documentation (TUL, usage logs, migration records) for a minimum of 5 years for audit defence.
Book a free consultation with our licensing specialists. No obligations, no vendor ties — just independent advice tailored to your situation.
Book Your Free Consultation →