Oracle's fiscal year ends May 31.
That date matters more than most organizations realize. For many enterprises, it represents the single best opportunity of the year to secure stronger pricing, more flexible terms, and meaningful structural improvements to long-standing Oracle agreements. Discounts of 70%, 80%, even north of 90% have been documented during this window — but not for organizations that show up unprepared.
The best outcomes go to companies who start preparing months in advance. This is Part I of our six-part EOFY series. It focuses on the most overlooked step in the process: internal audit and data gathering.
🎥 Watch the Part I webinar on Vimeo
---
Why Internal Audit Is the Foundation
Oracle's sales organization operates under significant pressure as May 31 approaches. Quotas are closing, deals need to finalize, and the leverage that creates is real — but only for organizations that arrive at the table with a clear position.
Without preparation, the dynamic inverts. A customer who doesn't understand their own deployment, entitlements, or contractual rights has no basis for negotiation. Oracle knows this. Signing under time pressure without understanding what you're agreeing to is one of the most expensive mistakes an enterprise can make.
"If the standard discount is 30%, towards the May 31st timeframe, we've seen discounts of 70%, 80%. Our current high watermark is 94.5% — a $100 million deal that ended up being less than $5 million." — Dean Bolton, Co-Founder, LicenseFortress
The window is real. The leverage is real. But it requires preparation.
---
What to Gather Before You Negotiate
The foundation of every successful EOFY engagement is a complete, organized set of Oracle documents. Most organizations don't have this. Contracts are scattered, POs are buried, and license metrics from agreements signed a decade ago are poorly understood.
Pull together:
- Oracle Master Agreement (OMA) — the governing document for all your Oracle purchases
- Ordering Documents / Order Documents — the specific products, quantities, and metrics you've licensed
- Support agreements and CSI numbers — the technical identifiers Oracle uses to track your entitlements
- Purchase Orders — often overlooked, but POs can contain terms and restrictions that materially affect your position
- ULAs, ELAs, and special agreements — each with different terms, restrictions, and certification requirements
Pay particular attention to agreement age. Older Oracle agreements often contain entitlements — including legacy backup and DR provisions like the Oracle 10-day rule — that are no longer available in modern agreements. These can be enormously valuable if identified before a renewal inadvertently replaces them.
Once entitlements are mapped, compare them against actual deployment. Run Oracle GLAS (formerly LMS) scripts across your environment to capture what's installed and running. Don't limit the audit to known Oracle systems — check environments where Oracle might have appeared undetected through shadow IT or cloud sprawl.
---
What Your Technology Stack Audit Must Cover
Contract and entitlement review tells you what Oracle says you're licensed to use. A technology stack audit tells you what's actually running.
Key areas:
- License metrics per product: What unit of measure governs your compliance? Processor counts differ by core factor. Named User Plus licenses carry minimums. Employee-based metrics cover populations you may not have accounted for.
- Virtualization rules: If Oracle software runs on VMware or any non-hard-partition hypervisor, Oracle's audit posture is that all physical cores in the cluster must be licensed — regardless of actual usage. This is Oracle policy, not contract — but you need to know it before the conversation starts.
- Cloud deployments: Running Oracle on AWS, Azure, or GCP creates licensing obligations that differ from on-premises. Understand your BYOL rights and any cloud-specific terms.
- Options and packs enabled by default: Diagnostics Pack, Tuning Pack, and others can be active in your environment without authorization. Without a license to cover them, they become audit findings.
Shadow IT is a consistent source of unexpected compliance exposure. Cloud infrastructure makes it easier than ever for Oracle deployments to appear in environments that were never part of the licensing conversation.
---
Why Consultants and Lawyers Both Have a Role
A common mistake is treating Oracle licensing consultants and Oracle licensing lawyers as interchangeable. They are not.
Consultants — including LicenseFortress — provide technical analysis: what's deployed, how it's configured, what the licensing implications are, and what options exist. That expertise is essential.
Legal professionals interpret the contract. They determine what Oracle can actually enforce, what language means in context, and what rights you hold that Oracle may not be acknowledging. When Oracle makes a claim — in an audit, in a negotiation, or in a renewal — the response must be grounded in contract law, not just licensing expertise.
"I am not a lawyer and I should never speak like a lawyer. When it comes to contracts and determining what is and what isn't, that belongs with a firm like Beeman & Muchmore. They need us for the technology piece — we need them for the legal piece." — Dr. Michael Corey, Co-Founder, LicenseFortress
The strongest EOFY outcomes combine both. Oracle's internal licensing policies — including the Partitioning Policy governing VMware environments — are not your contract. Your Oracle Master Agreement is. Every compliance claim and negotiation point must be evaluated against the actual contract language, not Oracle's published guidance.
---
What This Work Unlocks
Organizations that complete this groundwork before Oracle's fiscal year end consistently achieve better outcomes across every dimension:
Negotiation leverage. You cannot negotiate effectively without knowing your position. Verified entitlements, clean technology stack data, and a clear understanding of your contractual rights consistently produce better terms — lower costs, more favorable support structures, and greater flexibility.
Compliance risk reduction. A thorough internal audit surfaces compliance gaps before Oracle does. Discovering a $3 million exposure internally is a problem you can manage. Discovering it during an Oracle GLAS (formerly LMS) audit is a crisis with a much narrower set of options.
Budgeting accuracy. Knowing exactly what you have, what it costs, and what it will cost after renewal gives finance and procurement the data they need to plan accurately — without relying on Oracle's projections.
---
Where This Series Goes Next
- Part II: Analyzing license usage in detail
- Part III: Defining organizational goals
- Part IV: Building a negotiation strategy
- Part V: Mastering timing & execution
- Part VI: Post-signature safeguards
Schedule a consultation to start your EOFY preparation, or explore our Oracle Audit Defense services to understand your position.
