EBS Support Spend.

The largest line nobody examines.

For most organisations running Oracle E-Business Suite, the annual support fee is the single largest and least scrutinised line in the application budget. It is calculated as a percentage of the original net license fee, conventionally 22 percent per year, and it rises with each renewal under Oracle's support uplift policy. Because it arrives as a predictable annual invoice rather than a negotiated event, it tends to be paid without challenge year after year, even as the organisation's actual use of EBS shifts, shrinks, or stabilises. The result is that a great deal of EBS support spend bears little relationship to the value the organisation receives, and a disciplined review almost always finds room to bring it back under control. This article sets out where EBS support cost hides waste and the buyer side approach to optimising it.

How the 22 percent fee works.

Oracle support for EBS is priced as a percentage of the net license fee paid at the time of purchase, and that percentage is applied every year for as long as support is maintained. Two features of this model drive cost over time. First, the fee is anchored to the original license value regardless of how much the organisation now uses the licensed product, so a module bought years ago and barely used still attracts full support. Second, Oracle's repricing and uplift policies mean the fee tends to rise rather than fall, and attempts to drop individual licenses can trigger repricing of the remainder that erases the saving. Understanding these mechanics is essential, because they explain why EBS support feels immovable and why optimising it requires more than simply asking for a discount. The repricing trap in particular is one we navigate in our contract review service, and the support pricing logic across Oracle products is examined in our premier versus sustaining support article.

Finding the shelfware.

The first and largest source of EBS support waste is shelfware, meaning licensed modules and options for which the organisation pays support but which it no longer meaningfully uses. Over the life of an EBS estate, business change, reorganisations, and abandoned projects leave behind entitlements that continue to attract support indefinitely because no one revisits them. The optimisation work begins by reconciling every supported line against actual current usage, building an evidence based picture of what is genuinely in use and what is merely being paid for. This is more involved than it sounds, because Oracle's repricing rules mean that dropping a line is not always a simple subtraction, but identifying the shelfware is the necessary first step. Only once the organisation knows precisely what it uses can it make informed decisions about what to keep supporting. The licensing position behind this is connected to the customization exposure we cover in our EBS customizations article.

The third party support question.

One of the more significant levers available to mature EBS estates is third party support, where an independent provider takes over maintenance of a stable EBS environment at a fraction of Oracle's fee. For an organisation running a settled version of EBS with little appetite for new Oracle patches or upgrades, this can represent a substantial saving. The trade offs are real and must be weighed carefully: moving to third party support means giving up access to Oracle's patches, security updates, and the right to upgrade, and it can complicate any future return to Oracle support or migration to Fusion. The decision is therefore strategic, not merely financial, and it depends heavily on the organisation's roadmap. Where EBS is a stable, end state platform, third party support deserves serious analysis; where active development or a near term migration is planned, it rarely fits. We help clients model this decision objectively as part of our renewal negotiation service, and the migration alternative is examined in our Fusion cloud migration article.

Timing and the roadmap.

EBS support optimisation is most effective when it is aligned to the organisation's wider roadmap rather than treated as an isolated cost exercise. The right time to challenge support uplift, drop shelfware, or evaluate third party support is in the run up to a renewal, when the organisation has the leverage of an upcoming decision and the time to model the alternatives properly. Decisions made under deadline pressure, the subject of our deadline tactics article, tend to default to whatever Oracle proposes. By contrast, a support strategy that is sequenced against the renewal calendar and the migration plan lets the organisation optimise deliberately, capturing savings without compromising the platform or its future options. The full strategic frame sits in our EBS negotiation pillar guide and the reference detail in the Oracle Negotiation Playbook.

Bringing support spend back under control.

EBS support is large, recurring, and rarely challenged, which is exactly why it accumulates waste. The path to optimisation is methodical: reconcile every supported module against real usage, identify and address shelfware while modelling the repricing impact, challenge support uplift at every renewal, evaluate third party support against the roadmap honestly, and time every decision to maximise leverage. None of this requires confrontation with Oracle, only the discipline to treat the support invoice as a negotiable cost rather than a fixed fact. Done properly, it brings one of the largest lines in the IT budget back into proportion with the value the organisation actually receives.

Related resources.

• EBS Negotiation pillar guide
• Renewal Negotiation service
• Contract Review service
• Apps Unlimited deal type page
• Oracle E-Business Suite product page
• Oracle Negotiation Playbook 58 page reference paper.
• EBS Customizations and Licensing related sub article.