Oracle EBS Support Costs: What You're Really Paying

How Oracle Calculates EBS Support Fees

Oracle charges 22% of the net license value annually for Oracle Software Support on E-Business Suite products. The net license value is the amount you paid for your EBS licenses — after any discounts Oracle applied at the time of purchase. If Oracle gave you a 60% discount on a $10M list price, your net license value is $4M, and your annual support fee is $880,000.

This model has several characteristics that work in Oracle's favor:

• It is perpetual. Unlike a subscription that you can cancel, Oracle support on perpetual EBS licenses continues indefinitely. Stopping support means losing access to patches, updates, and Oracle's support portal — and potentially facing reinstatement fees if you want to return.
• It applies to all licensed products. You pay 22% on every EBS module you've ever licensed, whether you actively use it or not. A Financials module licensed in 2012 that your team stopped using in 2018 still generates annual support fees unless you formally terminate the license.
• It escalates over time. Oracle contracts typically include annual support fee increases — often 3-5% per year — that compound on top of the base 22% calculation. After five years, your support fee may be 15-25% higher than when you originally signed.

What Oracle EBS Support Actually Covers

Oracle Software Support for EBS provides access to Oracle's support portal (My Oracle Support), security patches, bug fixes, and cumulative update releases. For actively developed products with frequent regulatory requirements — payroll tax updates, for example — Oracle support delivers genuine value. The picture becomes less clear for stable, mature EBS deployments.

What You Get

• Access to My Oracle Support (MOS) — Oracle's knowledge base, patch downloads, and service request system
• Security patches and critical patch updates (CPUs), released quarterly
• Tax and regulatory updates for HR/Payroll modules (these have genuine compliance value)
• Bug fixes and defect resolution through Oracle's service request process
• Access to Oracle-certified patches for the operating system, database, and middleware layers when running the Oracle technology stack

What You Don't Get (But Often Assume You Do)

• New features or functional enhancements. Oracle Support does not fund development of new EBS capabilities. New features require separate product purchases or upgrades.
• Customization support. Oracle does not support custom code, modified standard code, or third-party integrations. Support applies to unmodified Oracle code only.
• Performance optimization. If EBS runs slowly due to database performance, custom report design, or infrastructure issues, Oracle Support will rarely resolve the root cause.
• Implementation assistance. Support is not consulting. Service request resolution often involves pointing to documentation rather than solving the operational problem.

Support Component	Included	Practical Value for Mature EBS
Security patches (CPU)	Yes	High — essential for security compliance
Tax/payroll regulatory updates	Yes	High — legally required for payroll accuracy
Bug fixes	Yes	Medium — fewer bugs in mature releases
My Oracle Support portal access	Yes	Medium — knowledge base useful, SR resolution variable
New features/enhancements	No	N/A
Custom code support	No	N/A
Performance consulting	No	N/A

Oracle EBS Support Lifecycle: Key Dates

Oracle's support lifecycle policy has significant financial implications for EBS customers. Understanding where your version sits in Oracle's support structure determines how much leverage you have in support fee negotiations.

Oracle's current support commitments for EBS versions:

• EBS 12.2: Premier Support through December 2031. This is the only version receiving full Oracle investment currently.
• EBS 12.1: Extended Support ended in 2018. Customers still on 12.1 are in Sustaining Support — they receive access to existing patches and fixes but no new patches, tax updates, or security patches.
• EBS 11i and earlier: Long past any formal support. Customers on these versions are effectively unsupported by Oracle regardless of what they pay for support.

The support lifecycle status of your EBS version directly affects the value you receive. If you are on EBS 12.1 in Sustaining Support, you are paying 22% annually for a significantly reduced set of deliverables compared to what 12.2 customers receive. This is a legitimate negotiating point for Oracle support cost reduction.

The Real Cost of Oracle EBS Support Over 10 Years

The compounding nature of Oracle support fees becomes clearer when viewed over a realistic horizon. Consider an organization that licensed EBS at a net license value of $5 million in 2016, with annual support fee escalation of 4%:

Year	Annual Support Fee	Cumulative Support Paid
Year 1 (2017)	$1,100,000	$1,100,000
Year 3 (2019)	$1,189,216	$3,379,216
Year 5 (2021)	$1,286,234	$5,857,898
Year 7 (2023)	$1,391,218	$8,655,780
Year 10 (2026)	$1,555,513	$12,988,221

By year 10, this organization has paid nearly $13 million in support fees — more than twice the original net license cost — for access to patches and a support portal. The asset they're supporting is a 10-year-old on-premises ERP system that Oracle is actively encouraging them to migrate away from.

Strategies to Reduce Oracle EBS Support Costs

Organizations have several proven approaches to reducing Oracle EBS support costs. The right strategy depends on your EBS version, how actively you use Oracle Support, and your migration plans.

1. Third-Party Support

Third-party Oracle support providers offer support for EBS at approximately 50% of Oracle's annual fee — sometimes lower. These providers employ former Oracle Support engineers who understand EBS deeply and can resolve service requests that Oracle's own support team often struggles with.

The key advantages of third-party support:

• Immediate cost reduction of 40-60% in year one
• Support for customizations and modified code — which Oracle explicitly does not support
• Named engineers who know your environment, rather than rotating tier-1 support queues
• No pressure to upgrade or migrate as a condition of support continuation

The key constraints to evaluate:

• No access to new Oracle-released patches after you leave Oracle Support. Your security posture must be managed through existing patches and configuration hardening.
• Tax and regulatory updates are handled differently — third-party providers deliver equivalent functionality through alternative mechanisms.
• If Oracle conducts an audit after you have left Oracle Support, the audit process and findings are unaffected — third-party support does not alter Oracle's audit rights.

2. License Rationalization Before Negotiation

Support fees are calculated on licensed products. If you have licensed EBS modules you no longer use, formally terminating those licenses reduces your support fee base. This requires a formal license termination process with Oracle — not simply stopping use — and carries nuances around how Oracle calculates the remaining contract value.

A thorough Oracle EBS licensing review can identify unused modules and quantify the support savings available through rationalization. In large EBS estates, this exercise frequently reveals six-figure annual savings.

3. Support Renewal Negotiation

Oracle negotiates support contracts. The leverage points available to you include: active evaluation of third-party support alternatives, planned migration to Oracle Cloud (which Oracle wants to accelerate), and support lifecycle status of your current version. Organizations that approach Oracle support renewal as a fixed cost leave significant savings on the table.

Our Oracle support cost reduction service provides experienced negotiators who have sat on Oracle's side of the table and know exactly what Oracle can and will offer when properly motivated.

4. Desupport with Frozen Support

Some organizations choose to leave Oracle Support entirely — accepting no new patches — and rely on their existing patch baseline. This is viable only for organizations with strong internal security capabilities and stable regulatory environments. For EBS Financials or Payroll deployments, regulatory changes make this approach risky for most organizations.

Oracle Support Fee Reinstatement: The Hidden Trap

Organizations that let Oracle support lapse face a reinstatement fee if they want to return to Oracle Software Support. Oracle's standard reinstatement policy requires payment of all back support fees from the date support lapsed to the date of reinstatement, plus an additional reinstatement surcharge (typically 150% of one year's support fee). This creates a financial trap that makes leaving Oracle Support a one-way decision for most customers.

This is why the decision to leave Oracle Support — whether for third-party support or complete desupport — must be made with full analysis of the long-term implications. Read our detailed guidance at Oracle Licensing White Papers before making this decision.

EBS Support and Oracle Audits

Being on Oracle Support does not reduce Oracle's audit rights or protect you from license compliance findings. Oracle's License Management Services (LMS) team conducts audits independently of the support relationship. Customers who have paid 22% annually for decades are audited on exactly the same basis as customers who have just signed their first Oracle contract.

Conversely, leaving Oracle Support does not trigger an audit. Oracle's audit programs are driven by their own internal metrics, not by support status. The connection between support costs and audit risk is a misconception Oracle benefits from — customers who fear that leaving support will attract audit attention are more likely to stay on support.

For comprehensive guidance on Oracle's audit process, see our Oracle Audit Defense Guide.

Building a Business Case for EBS Support Reduction

Reducing Oracle EBS support costs requires building a clear business case for your finance and IT leadership. The key elements of that case are:

1. Quantify the 10-year cost trajectory. Show leadership the full compounding cost of current support fees through your expected EBS end-of-life or migration date.
2. Assess third-party support risk. Provide a factual assessment of what third-party support provides and doesn't provide, specific to your EBS version and usage patterns.
3. Identify migration timeline clarity. If you have a defined Oracle Cloud migration timeline, the business case for third-party support or reduced support until migration becomes significantly stronger.
4. Calculate net present value of savings. A 50% reduction in annual support fees, compounded over 5 years, represents a present-value saving that most organizations can justify the transition costs of.

For case studies of organizations that have successfully reduced their Oracle EBS support costs, see our client case studies. Not affiliated with Oracle Corporation.