ULA certification, the number originates with you
Certification is not an audit Oracle runs: it is a declaration you sign under an officer's signature, stating how much of each ULA product was installed and running on the certification date. Oracle converts that number into perpetual licenses, it becomes the permanent ceiling you own, and everything a ULA is worth is decided in one short document, a letter with quantities in it.
Prepared by Redress Compliance · August 7, 2026 · Oracle advisory. Based on 30 to 40 ULA certifications run or reviewed 2024 to 2025.
Executive summary
The ceiling and the annuity both set at the signature.
Every processor deployed during the term is free, the first one above the certified number is a full price purchase at the moment your leverage is lowest, and support attaches to the count forever at roughly 22 percent of net license fee per year: the quantity you declare sets an annuity.
Not just an entitlement.
Because it is a declaration and not an audit, your job is to build a number you are willing to sign, then hold it, with discovery, reconciliation, and legal review all running on your calendar.
Non production is the routinely missing half. Oracle licenses development, test, QA, and training on the same basis as production, and non production was missing from the first draft in more than half of our engagements, usually because discovery ran against production subnets only.
The counting test in your clause, installed, installed and running, or in use, decides whether idle and standby estate counts, and the three wordings are different tests.
The countersignature is the evidence almost nobody requests. Roughly four in five declarations went out without any request for a countersigned quantity schedule, leaving the buyer's only proof of entitlement, three years later, a letter they wrote themselves.
The declaration that holds up is boring and specific, products by full Oracle name, quantities with metrics, one date used consistently, signed by the officer the clause names on the contracting entity's letterhead, delivered by the method the contract specifies.
And closed with the countersignature request.
The clause is the deadline and the cloud is contract specific. Most ordering documents give 30 days after the end date, some 60 or 90, and the failure consequences differ: reversion to prior entitlement in the common version, deemed zero for products with no prior entitlement in the harsher one.
Post 2019 ordering documents commonly exclude authorized cloud or cap it at a trailing average, and where the trailing average applied, capacity added in the final months moved the certified number by a few percent at most.
The clause extraction, before anything else
| Clause element | What to look for | Why it moves the number |
|---|---|---|
| The window | 30, 60, or 90 days; calendar or business | Sets the last date a reconciliation error can still be fixed |
| The counting test | Installed, installed and running, or in use | Decides whether idle and standby estate counts |
| The entity definition | Named entities, ownership thresholds, acquisition language | Acquired estate only counts if the definition reaches it |
| The cloud treatment | Silence, exclusion, or a trailing average cap | Worth thousands of processors either way |
| The signatory | The officer title and contracting entity | A wrongly signed letter is a challengeable letter |
| The failure consequence | Reversion to prior entitlement, or deemed zero | Sets the true cost of missing the date |
If the window closes without a declaration, the common outcome is reversion.
You fall back to whatever perpetual licenses you held before the ULA started, which on an estate that tripled during the term is a compliance gap rather than an entitlement, and the harsher variant deems zero for products with no prior holdings.
Renewal does not remove the event: a renewal still closes the expiring term, requiring certification or folding the old quantities forward, on terms worth reading before the renewal conversation starts.
The letter itself, boring and specific
- The reference: the ordering document number and the ULA term dates, anchoring which contract the quantities certify.
- The date: the certification date stated once and used consistently through every quantity.
- The products: each ULA product by its full Oracle name, never an internal abbreviation, with the license metric beside each quantity.
- The scope statement: that the quantities reflect programs installed and running as of the date, within the licensed entity scope.
- The countersignature request: that Oracle acknowledge and countersign the schedule, the line four in five letters omit and every later dispute wishes existed.
The Oracle ULA decision framework
The full instrument end to end: the entry decision, the deployment run, the certification mechanics, and the renew or exit fork priced both ways.
Get the white paper →The twelve month run, discovery on your calendar
Because nothing in the clause obliges you to run Oracle's scripts to produce your own declaration, the preparation runs on your tooling and timeline: full estate discovery including the non production subnets the first drafts always missed.
The counting test applied per the clause wording rather than habit, the entity scope reconciled against the definition, and the cloud position read from your own ordering document, because post 2019 versions differ and the trailing average cap makes late capacity additions nearly worthless.
The deployment maximization decisions, what to stand up inside the free window before the ceiling fixes, belong to the final year and are worked in the ULA renewal tactics, with the wider instrument, entry through exit.
In the Oracle ULA guide and the post certification life in the exit strategy guide.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across certifications, 2024 to 2025
Across the 30 to 40 Oracle ULA certifications Fredrik Filipsson ran or reviewed in 2024 and 2025, the declaration itself was rarely the problem; the preparation behind it was:
Leaving the buyer's only entitlement evidence, years later, a letter they wrote themselves.
Where the ordering document capped cloud at a trailing average, final month additions barely registered.
The strategic frame holds the details together: the certified number is a ceiling you will live under and an annuity you will pay on, which makes under declaration the expensive humility, every processor of estate not counted is a purchase later at zero leverage.
And over declaration the expensive vanity, every phantom processor is 22 percent a year forever.
The number you want is the defensible maximum, non production included, entity scope fully reached, counted under your clause's own test, and countersigned. The perpetual variant's different mechanics are covered in the PULA analysis.
Your first five moves
- Pull the ordering document and extract the six clause elements, because the window, the counting test, and the failure consequence shape the whole project.
- Run discovery across every subnet, non production included, since development, test, QA, and training all count and half the first drafts missed them.
- Reconcile the entity scope against the definition, because acquired estate counts only where the language reaches it.
- Read your own cloud clause, exclusion or trailing average, before anyone plans a final month deployment push.
- Request the countersigned quantity schedule, the one line that converts your letter into evidence. The Oracle practice runs the certification with you.
Frequently asked questions
Is Oracle ULA certification an audit?
No: it is a declaration you sign under an authorized officer's signature, stating the quantity of each ULA product installed and running on the certification date, which Oracle converts into perpetual licenses.
Oracle does not count your estate and hand you a number; you produce the number, and discovery, reconciliation, and legal review all run on your calendar.
How long do you have to certify an Oracle ULA?
Whatever your clause says: most ordering documents give 30 days after the end date, a meaningful minority give 60 or 90, and the trigger, calendar versus business days, and delivery method all live in the same clause.
Missing the window commonly reverts you to pre ULA entitlements, and some contracts treat silence as certifying zero for products with no prior holdings.
Does non production count in ULA certification?
Yes: Oracle licenses development, test, QA, and training on the same basis as production, and non production was missing from more than half of first draft declarations in our engagements, usually because discovery ran only against production subnets.
Under counting it converts free term deployments into full price purchases later.
Can cloud deployments be certified in a ULA?
Contract specifically: ordering documents written after 2019 commonly exclude authorized cloud environments or cap them at a trailing average of usage, and versions differ enough that only your own clause answers.
Where the trailing average applied, capacity added in the final months moved the certified number by a few percent at most, which kills the late push strategy.
What is a countersigned quantity schedule and why does it matter?
Oracle's written acknowledgment of your certified quantities: without it, your only evidence of entitlement three years later is the letter you wrote yourself.
Four in five declarations in our file went out without requesting one, and the request costs a sentence at the moment of maximum documentation and prevents the dispute at the moment of maximum exposure.
Should you certify high or low on a ULA?
Neither: certify the defensible maximum. Under declaration converts uncounted estate into future purchases at zero leverage; over declaration attaches 22 percent annual support to phantom processors forever.
The right number is everything genuinely installed and running under your clause's counting test, entity scope fully reached, non production included, and countersigned.
