§ White paper · 52 pages · 2026 edition
The Oracle Audit Defense Handbook.
A practical guide for procurement, IT and legal teams when Oracle's License Management Services arrives. How to read the audit letter, run ASR scripts on your terms, manage deployed data, and settle for less.
§ I · What you will learn
- How to read an Oracle LMS audit notification letter and what to do in the first 72 hours before responding.
- What ASR scripts actually collect, where the discretion lies, and how to negotiate the scope before they are run.
- How Oracle calculates a deployed but unlicensed compliance gap and where the most common counting errors happen.
- Standard Oracle settlement playbook including ULA conversions, term license uplifts and cloud offset trades.
- How to build a defensible counter position and the documents you need ready before the first Oracle meeting.
- When to bring in independent counsel, when to escalate inside Oracle, and when to settle versus when to push back.
§ II · Table of contents
- The Oracle audit landscape and how LMS engagements actually unfold
- Reading the audit letter and the first 72 hour response protocol
- ASR scripts decoded with what they collect and how the discretion is structured
- Deployed data, counting methods and the most common Oracle errors
- Settlement structures including ULA conversion, term uplift and cloud offset
- Building the counter position with a buyer side analyst lens
- When to settle, when to escalate, and when to bring in independent counsel
§ III · Who it is for
Audience 01
Procurement leaders managing an active audit
Audience 02
CIOs and IT directors with deployed Oracle estate
Audience 03
Legal and contract counsel reviewing LMS findings
Audience 04
CFOs budgeting for potential settlement exposure
The audit letter is not a verdict. It is the opening move of a negotiation that will run for six to eighteen months. The settlement number Oracle proposes first is almost never the number that is signed.
From the introduction