The certification clause is the most valuable paragraph in your ULA, because it sets the rules for converting unlimited deployment into a permanent entitlement. Reading it phrase by phrase, before the window opens, is how you find the value and avoid the traps.
Most ULA holders read the certification clause once, when they sign, and never again until the window is open and the clock is running. By then the words are no longer something to plan around. They are constraints you are living inside. This article reads a typical certification clause the way we read it on the buyer side, slowing down on the phrases that decide your number. Exact wording varies, so treat this as a guide to what to look for in your own agreement rather than a substitute for reading it.
In plain terms, the clause requires you to declare, within a set period around the end of the term, the quantity of each licensed product you have deployed, and to certify that quantity in a letter signed by an authorized executive. That declared quantity becomes your perpetual entitlement, and the unlimited deployment right ends. Everything else in the clause is detail that shapes how that core mechanic plays out.
The clause sets a window, often thirty days, sometimes more, in which the certification must be delivered. This is a hard deadline, and it is the reason the real work has to happen before the window opens. By the time the window is live, you cannot meaningfully change your deployed position, only declare it. Read this phrase as a date to work backwards from, ideally about 18 months, not as the moment to begin.
This names the metrics you will certify. Processor counting applies a core factor to the cores in scope, then rounds per the agreement. Named User Plus applies where the product and the contract use that metric. The phrase matters because it defines the units of the declaration. If your estate mixes metrics, the clause tells you which products are counted which way, and a miscount in either direction is locked in once you sign.
The verb here is doing enormous work. Some clauses count what is deployed, some what is installed and running, and the difference can move a number. This phrase is also where the timing question lives: deployments generally must be in place within the term to count. A workload you stand up the week after expiry is not part of the certified position. Reading this phrase early is what lets you deploy with purpose while there is still time.
Two short words that reach back to the customer definition at the front of the agreement. Only entities inside that definition may deploy under the ULA, and only their deployments count at certification. After a merger or acquisition this phrase becomes a flashpoint. A newly acquired entity deploying Oracle is usually outside the customer definition unless the agreement was amended, and its deployments can sit outside scope. The same logic cuts the other way: deployments by an in scope entity in an unexpected location may still count.
Many ULAs limit the agreement to a defined territory. Deployments outside that territory may not count toward your certified entitlement, and worse, they can trigger a remediation demand as unlicensed use. For a multinational, this single phrase can decide whether a regional data centre is an asset or a liability at exit. It needs reading against where your Oracle workloads actually run, not where the contract assumed they would.
If your agreement addresses cloud at all, this is where it does. Cloud counting is contract specific. Many ULAs require a deployment in AWS or Azure to run for 365 continuous days before it counts toward the certification baseline. Some exclude public cloud entirely. Many are simply silent, and silence is not inclusion. Where the words do not let cloud count, eligible workloads can be repatriated on premises or moved to OCI before exit so they do. This is the clearest example of a phrase whose meaning depends entirely on your specific contract language.
The certification is an attestation, not a form. The clause typically requires a senior, often C level, signatory, and that person is personally attesting that the declared count is accurate. The practical consequence is that the signer needs the evidence file behind the number before they sign: server lists, tool output, and a written methodology. A signature on a number nobody can defend is an audit exposure with an executive name on it.
The table below summarises how we read each phrase and what to check in your own agreement. It is a reading aid, not legal advice, and the meaning of any clause turns on its exact wording.
| Phrase | What it controls | What to check |
|---|---|---|
| Within X days of expiry | The certification deadline | Work backwards about 18 months |
| Processors and Named User Plus | The metrics declared | Which products use which metric |
| Deployed within the term | What and when counts | Deploy with purpose before expiry |
| By the Customer | Which entities count | Scope after any M&A |
| Within the Territory | Where deployment counts | Where workloads actually run |
| Public cloud language | Whether cloud counts | Continuous run tests and silence |
| Signed by an executive | Who attests | Evidence file before signature |
Every phrase above rewards advance reading and punishes a late start. The deadline is fixed, so preparation needs a runway. The deployment verb only helps you if there is still time to deploy. The customer and territory clauses can be managed during the term but rarely in the window. The cloud language often calls for a 365 day continuous run, which by definition has to begin a year before exit. None of this is available to the team that opens the clause for the first time when the window does.
The certification clause is not paperwork at the end. It is the rulebook for the most valuable transaction in the ULA. Read it on the buyer side, early, and it tells you exactly where your entitlement is won.
To see how this clause sits within the wider arc of the agreement, read the ULA lifecycle from signature to exit. To understand why a growing estate gets more from these same words than a flat one, read why ULAs reward growth and punish flat estates. For the full exit mechanics, start with the Oracle ULA certification guide.
It typically requires you to declare, within a set period around expiry, the quantity of each product you have deployed, certified in a letter signed by an authorized executive. That declared quantity becomes your perpetual entitlement and the unlimited right ends.
The clause usually names an authorized executive officer, often a C level signatory. Because the signature attests to the count, the person who signs needs the evidence file behind the number before they sign.
Send us your expiry date and we will walk your certification clause phrase by phrase and tell you where your value sits.