A strategic guide for CIOs and IT procurement leaders navigating SAP's maintenance reinstatement policy. Covering back-maintenance fees, reinstatement penalties, strategies to avoid paying full back fees, licence considerations, system currency requirements, cost-benefit analysis, and a negotiation checklist for returning to SAP support on your terms.
This guide is part of our SAP licensing advisory series. See also: SAP Third-Party Support Guide · Best SAP Third-Party Providers Compared · SAP Contract Negotiation Service
Rejoining SAP's support programme after a period with third-party maintenance can be complex and costly. Organisations often leave SAP maintenance to save money with independent providers, but later find reasons to return. The decision to resume SAP support should be made strategically, with a clear understanding of fees, risks, and negotiation tactics. Read our guide to SAP Third-Party Support.
Many SAP customers turn to third-party support from independent firms to cut costs. After enjoying significant savings (typically 50% of SAP's standard maintenance fees) there are scenarios where moving back to SAP maintenance becomes strategically necessary.
In short, the cost-saving phase with third-party support may come to an end once strategic needs arise. Access to SAP's latest technology, official support infrastructure, and the assurance of vendor backing often pull organisations back to SAP's maintenance fold.
SAP's maintenance return policy is notoriously strict. If you want to resume SAP support after time away, be prepared for reinstatement fee surprises.
SAP's default position: SAP typically requires payment of all back-maintenance fees for the period you were off support, plus a penalty surcharge for reinstatement. If you left SAP support for three years, SAP will demand those three years' worth of support fees you "skipped" (often 20%+ of your licence value per year) and add a surcharge (commonly an extra 10-20% of the total) as the reinstatement penalty. The bill to rejoin can equal or even exceed the cost of buying a new licence outright.
The policy makes it financially painful to take a maintenance "holiday." SAP wants to discourage customers from leaving support in the first place. The punitive structure is designed to make the savings from third-party support appear illusory once the full lifecycle cost is calculated.
SAP aims to recover the fees as if you had never departed. From their perspective, you received the benefits of their software (via a third party) without paying SAP, and now must "catch up" on dues. The back-maintenance demand is SAP's mechanism for ensuring no customer benefits from a support gap without financial consequence.
The reinstatement cost often negates the savings you enjoyed with third-party support, which is exactly the point from SAP's perspective. SAP wants the financial outcome of leaving and returning to be no better (and ideally worse) than having stayed on SAP support continuously.
SAP may review your licence compliance before welcoming you back. If your usage grew while off support (additional users, modules, indirect access), SAP could demand you purchase those licences and pay maintenance on them retroactively. The reinstatement process becomes an effective audit by another name.
Reinstatement cost example: Annual SAP maintenance: $500,000/year. Off support for 3 years with 15% penalty surcharge. Back-maintenance: $500K x 3 years = $1,500,000. Reinstatement penalty: $1,500K x 15% = $225,000. Total reinstatement bill: $1,725,000. Compare this to the ~$750,000 you saved during those 3 years on third-party support ($250K/year vs $500K/year). Net cost of the "holiday": approximately $975,000, worse than if you had never left.
Facing a massive reinstatement invoice, many companies look for creative ways to return to SAP support more affordably. While SAP's default is to charge every penny of back maintenance, there are strategic approaches to rejoin on significantly better terms.
In every engagement where we have helped clients return to SAP support, the organisations that secured the best outcomes were those that treated the reinstatement as a commercial negotiation with SAP, not an administrative process. SAP's default position is to demand full back-maintenance plus a penalty surcharge, but when the client brings a credible S/4HANA roadmap and competitive alternatives to the table, the back fees consistently get reduced by 50-100%. The single worst approach is to accept SAP's first quote and pay the full reinstatement invoice without challenge.
When you left SAP support, you did not lose your SAP licences. Those are perpetual. You retain the legal right to use the software you paid for, even during your third-party support period. Understanding this is critical: your existing licences are the foundation for any return. You are not a new customer. You already own the software.
Watch for licence growth. If you added users, expanded to new modules, or grew SAP usage while off support, prepare to address that now. SAP will require you to properly licence any expansions and may demand back-maintenance on unlicensed use.
Conduct a compliance self-audit first. Before contacting SAP, conduct an internal licence review. Confirm your user counts, module usage, and indirect access scenarios against what you have licensed. Being proactively aware of any compliance gaps puts you in a better position to negotiate and avoid surprises. You might even choose to true-up licences before or as part of rejoining, to show good faith and control the pricing of those licences, rather than waiting for SAP to discover discrepancies and charge list price with penalties.
Protect your existing terms. Ensure any new agreement maintains or improves your existing terms. If you had discounts, special pricing, or favourable conditions in your original contract, try to preserve them. The reinstatement is effectively a new contract. Treat it with the same rigour as any major procurement agreement.
A practical challenge when returning to SAP maintenance is ensuring your systems are "current" enough for SAP to support. If you have been away for several years, your SAP software release might now be outdated or past its supported lifecycle. SAP typically will not provide full support for very old versions, so rejoining may require an upgrade as part of the process.
Check the version and patch level of your SAP ERP, database, and other components. If you left at ECC 6.0 on an older enhancement pack, that version might now be out of mainstream support. SAP may mandate that you apply all the latest support packs or upgrade to a minimum release before they will officially take you back on support. During third-party support, you likely did not receive new releases, so there could be a significant leap to the current supported version.
Planning an upgrade or patch catch-up can be a substantial project. Factor this into your timeline and budget for returning to SAP. You might need several months to get systems up to a supported release, and potentially the help of SAP or a consulting partner to perform the upgrade. Make sure the cost-benefit analysis of returning includes these project costs. If you must spend heavily on an upgrade and pay reinstatement fees, the justification for returning should be proportionally stronger, like a pending S/4HANA migration that delivers its own business value.
Any rushed upgrade just to satisfy support requirements carries risk. Schedule necessary upgrades in a controlled manner. If possible, coordinate rejoining SAP support after you have upgraded. In some cases, companies negotiate a short grace period: they rejoin support and immediately undertake the required upgrade with SAP's agreement. SAP may offer limited support during that interim if you agree on a plan to become current. Clarify these expectations in the contract. Avoid a scenario where you pay to rejoin and then discover SAP will not help until you upgrade.
Before signing any agreement to return to SAP maintenance, run a thorough cost-benefit analysis. Rejoining SAP support is a significant financial decision, sometimes running into millions of dollars when all factors are included.
| Cost Factor | Description | Example |
|---|---|---|
| Back-maintenance + penalty | SAP's default reinstatement invoice: all years of unpaid maintenance plus 10-20% surcharge | 3 years x $500K + 15% = $1.725M |
| New licence/subscription (alternative) | If buying fresh S/4HANA licences or RISE subscription instead of reinstating | $2M for S/4HANA with year 1 support included |
| Upgrade project costs | Technical upgrade to reach a supported release (consulting, testing, downtime) | $200K-$2M+ depending on complexity |
| Third-party savings achieved | Money saved during the period on third-party support (~50% of SAP fees/year) | 3 years x $250K savings = $750K |
| Ongoing annual maintenance | Future SAP support fees once reinstated (20%+ of licence value per year) | $500K/year ongoing |
Key insight: when rejoining makes financial sense. Rejoining SAP support only makes clear financial sense if it is enabling a larger initiative: a major upgrade, cloud migration, or merger that requires standardisation. Rarely is it worth paying a massive sum just to return to steady-state support for an old system. In many cases, companies conclude that staying with third-party support until a defined migration event is more cost-effective, unless SAP offers a surprisingly good deal to return.
If you decide that returning to SAP support is the right path, approach the conversation with SAP as a negotiation. Here is a tactical checklist to prepare for and execute a favourable deal.
Rejoining SAP support after third-party maintenance is a significant decision. By staying strategic, focusing on your leverage, and planning the move like a tactical negotiation, you can minimise costs and risks. The key is to be in control of the process. Do it on your terms, aligned with your business roadmap, rather than as an emotional or rushed reaction. With careful planning and negotiation, you can return to SAP support in a way that supports your organisation's goals without breaking the bank.
No. SAP licences are perpetual. You retain the legal right to use the software you purchased regardless of whether you maintain an active SAP support contract. Leaving SAP maintenance does not invalidate your licences. What you lose is access to SAP's support services: new patches, enhancement packs, version upgrades, and the ability to open support tickets with SAP directly. Your third-party provider covers break-fix support during that period, but cannot deliver new SAP-developed software. When you return to SAP support, you are reinstating maintenance on licences you already own, not purchasing the software again (unless you choose to take the "new licence" path as a negotiation strategy).
SAP's default reinstatement cost is all back-maintenance fees for the years you were off support, plus a penalty surcharge of 10-20%. For example, if your annual maintenance was $500,000 and you were off support for three years, the reinstatement bill would be approximately $1.5 million in back fees plus $150K-$300K in penalty surcharge, totalling $1.65M-$1.8M. However, this is SAP's opening position, not the final price. Through negotiation, particularly when combined with new SAP purchases (S/4HANA, RISE subscriptions), companies regularly secure reductions of 50-100% on back-maintenance fees. The actual cost depends heavily on your negotiation leverage, future SAP investment plans, and timing.
SAP can, and often does, review your licence compliance as part of the reinstatement process. This is not a formal "audit" in the contractual sense (since you may not have an active audit clause while off support), but SAP will typically request information about your current SAP usage before agreeing to reinstate maintenance. If your usage grew while off support (more users, additional modules, indirect access through integrations), SAP could require you to purchase those licences and pay maintenance on them retroactively. This is why conducting an internal compliance self-audit before approaching SAP is critical. Understanding your actual position lets you address gaps proactively, control the pricing, and avoid being caught off guard with list-price demands.
In many cases, yes, particularly if you have been off support for three or more years. SAP's reinstatement invoice for multi-year back-maintenance plus penalty surcharge can approach or exceed the cost of purchasing new S/4HANA licences, and the new-licence route comes with the added benefit of current software, a clean contract, and no legacy baggage. SAP also offers conversion credits and incentives to migrate from ECC to S/4HANA, which can further reduce the effective cost of the "fresh start" approach. The right answer depends on your specific numbers: compare the total reinstatement cost (back fees + penalty + ongoing maintenance) against the total new-licence cost (purchase price + first year maintenance + migration project) and evaluate which delivers better value aligned with your IT roadmap.
The best timing aligns with SAP's commercial incentives. SAP's fiscal year ends on December 31, so negotiations in Q4 (October-December), and particularly in the final weeks of December, often yield the best pricing and most flexibility on back-fee waivers. SAP sales teams are under pressure to close deals and hit annual targets, making them more willing to offer concessions on reinstatement terms. Quarterly close periods (end of March, June, September) also create similar dynamics. Beyond SAP's calendar, the best strategic timing is when you have a credible S/4HANA migration plan or new SAP investment to offer. This gives SAP a revenue story that justifies waiving or reducing back-maintenance fees internally.