The invoice arrives every January, it is calculated as a percentage of a licence you bought years ago, and almost nobody in the business can explain what it buys. In 2008 a critical mass of ERP customers finally said so out loud. The trigger was SAP's decision that year to move customers to Enterprise Support at 22 percent of licence fees annually, replacing the standard programme most of them were on. Oracle was already charging a comparable rate. The increase was modest in percentage terms and enormous in principle, because it forced every CIO to do arithmetic they had been avoiding.
The Arithmetic Nobody Wanted to Do
At 22 percent per year, a customer repurchases the entire software licence roughly every four and a half years. Over a ten-year system life — conservative for ERP, where fifteen is common — maintenance costs more than double the original licence. Put differently: the licence is the deposit. Maintenance is the actual price. What that annuity buys, according to the contract, is four things: corrective patches, legal and regulatory updates, access to technical support, and the right to install new versions when they are released. The fourth item is where the 2008 argument caught fire. Customers had the right to new releases and no ability to use it, because installing a major ERP upgrade costs multiples of the licence in integration, testing and change management. Organizations were paying an annuity for upgrade rights they could not afford to exercise, on a system they had customised so heavily that upgrading meant re-doing the modifications. Strip out the unexercisable upgrade rights and the value proposition reduces to regulatory updates and a support desk. Both are worth real money. Neither obviously costs 22 percent of a multi-million dollar licence every year.
What Happened to the Revolt
User groups pushed back hard, particularly in Germany, and the pressure worked in stages. SAP eventually made pricing concessions, tied support price increases to measurable benchmarks agreed with international user groups, and ultimately restored the standard support option that the Enterprise Support transition was meant to eliminate. That outcome is worth remembering, because it is unusual. Collective, organised, publicly articulated customer pressure changed a major vendor's pricing model. Individual renewal negotiations almost never do. The second consequence was the arrival of a real third-party support industry. Independent providers offering support at roughly half the vendor rate had existed before 2008; the fee increase gave them a market. The legal environment around them was contested — SAP's TomorrowNow subsidiary was wound down amid litigation with Oracle during the same period — but the category survived and has since become a standard line in ERP sourcing strategy.
Why Vendors Defend the Rate So Hard
Maintenance revenue is the most valuable line on an enterprise software vendor's income statement. It is recurring, high-margin, and grows with the installed base rather than with new sales. It funds research and development, smooths out licence-sale volatility, and underwrites the valuation multiple. Which creates a structural conflict that every ERP customer should understand clearly. Your maintenance payments fund development of the vendor's next-generation product — typically the cloud platform you will later be asked to migrate to, at additional cost. You are financing the construction of your own replacement system, and your leverage to object declines every year that your customisations deepen. The modern version of this dynamic is the migration deadline. Vendors set end-of-mainstream-maintenance dates for legacy suites, offer extended support at a premium, and price the successor platform as the path of least resistance. The mechanism is unchanged from 2008; only the destination is different.
| Component | Contract question | Operating evidence |
|---|---|---|
| Support | What incident support and escalation are included? | Tickets, severity and resolutions actually used. |
| Updates | Which patches and legal updates are provided? | Applicability, testing and installation history. |
| Upgrades | What rights are included, and what work is excluded? | Planned release path and implementation effort. |
| Exit | What happens on cancellation or a change of provider? | Entitlements, data access and transition obligations. |
Qualitative summary of this article's source text, not a measured outcome or performance estimate.
Getting Control of the Number
- Calculate maintenance as a share of ten-year total cost. Present it to the board as a single figure. In most ERP estates it is the largest single line, and most boards have never seen it isolated.
- Audit what you actually consume. How many support tickets did you raise last year? How many were resolved by the vendor rather than your integrator? Which patches did you apply? Organizations frequently discover they log fewer than a dozen vendor tickets a year against a seven-figure support bill.
- Separate regulatory updates from everything else. Tax, statutory reporting and payroll updates are the component with genuine ongoing value, particularly in fast-moving regimes like the GCC's e-invoicing and tax rollouts. Price that separately in your own analysis, because it is the part you cannot self-provide.
- Read the escalation clauses. Many contracts permit annual increases indexed to inflation or a stated percentage. Compounded across a decade, the clause matters more than the headline rate.
- Audit shelfware. You pay maintenance on licences whether or not they are deployed. Unused modules and lapsed user counts are the fastest available saving and require no negotiation at all in some contracts.
- Evaluate third-party support seriously, with legal review. For a stable system you do not intend to upgrade, it can halve the cost. The trade-offs are real: no new versions, no vendor-delivered patches, and complications if you later return to vendor support or migrate.
- Negotiate at the moment of leverage. Maintenance terms are easiest to change when you are buying something else. A renewal in isolation gives you almost nothing to trade.
- Decide the endgame explicitly. If you will migrate to the vendor's cloud platform within three years, paying full maintenance is defensible. If you intend to run the current system for another decade, you are financing a roadmap you will never use.
The Question That Still Has No Good Answer
Eighteen years after the revolt, most ERP customers still cannot say what proportion of their maintenance fee is consumed by support they actually use. They renew because the alternative requires analysis nobody has been assigned to do. The 2008 dispute did not settle whether 22 percent is the right number. It settled something more useful: that the number is negotiable, that organised customers get better outcomes than isolated ones, and that a support fee nobody can justify is a strategy question rather than a procurement formality.
Common Questions
Why are ERP maintenance fees 22 percent?
Because the market has tolerated it. The rate reflects vendor economics — recurring high-margin revenue that funds R&D and valuation — rather than the delivery cost of the support provided.
Is third-party ERP support safe?
It is an established market for stable systems, typically at around half the vendor rate. The trade-offs are no new releases, no vendor-issued patches, and potential friction if you return to vendor support later. Review the contractual and IP terms carefully before switching.
What does ERP maintenance actually include?
Corrective patches, legal and regulatory updates, technical support access, and rights to new versions. The last of these is the least used, because major upgrades cost far more than the licence itself.
How can we reduce ERP support costs without switching?
Eliminate shelfware, right-size user counts, challenge escalation clauses, consolidate contracts across entities, and negotiate support terms as part of a larger purchase rather than at standalone renewal.
Maintenance Cost Review — Outpace quantifies what your ERP support contract costs over a ten-year horizon, measures what your organization actually consumes against it, and builds the negotiating position or alternative sourcing case that follows from the numbers.