Certifying out of a ULA is not an audit. It is your own declaration of deployed quantities under the agreement. A complete, well evidenced certification keeps the process a declaration you control, rather than an examination Oracle runs.
Many ULA holders treat certification and audit as the same event. They are not. Certification is a contractual step you take to convert deployment into a permanent entitlement. An audit is a separate right Oracle holds to examine your usage. Confusing the two leads organisations to hand over more than the certification requires, and to run vendor tooling they were never obliged to run. Keeping the two processes distinct is one of the simplest ways to protect your position.
Certification is not an audit, and a clean certification does not, by itself, invite one. When you certify, you declare your deployed quantities and the count converts to perpetual licences. Oracle may review the declaration, but the process is a contractual exchange, not an investigation. The risk of attracting closer attention rises when the count is thin, inconsistent, or unsupported by evidence, because that is what prompts questions. A complete count with a clear evidence file behind it gives a reviewer little to pull at.
This is why preparation is the best protection. The organisation that walks into the certification window already knowing its number, with the evidence assembled, is not reacting to Oracle. It is presenting a finished position. The organisation that arrives unprepared, scrambling to assemble a count under time pressure, is the one that ends up leaning on vendor processes and exposing more than it needs to.
Running Oracle License Management Services scripts is a choice, not an obligation, unless your specific contract states otherwise. You are entitled to build your certification count from your own discovery tooling, your own inventory, and your own records. The scripts produce output Oracle is familiar with, which has value in some situations, but running them also shapes exactly what the vendor sees and on whose terms.
The decision deserves analysis rather than reflex. In some engagements running the scripts is sensible. In others it surrenders control of the narrative for no gain. The right answer depends on the state of your data, the products in scope, and the certification clause in your agreement. Treat the question as a deliberate choice, not a default.
Certification is a contractual declaration you initiate at the end of the term to convert deployment into perpetual licences. An audit is a separate examination Oracle initiates under its audit rights, usually with a formal letter. The first is yours to control and prepare. The second is governed by different clauses and a different posture. Do not let one bleed into the other.
Three habits keep the process clean. First, measure your own deployment independently and early, so the number you certify is one you built, not one assembled for you. Second, assemble the evidence file as you go, meaning server lists, tool output, and a written methodology, so every line in the count can be explained. Third, reconcile the count to the contract before anything goes to Oracle, confirming products, customer definition, and territory all align. With those in place, the certification letter is a finished statement, and there is little reason for the exchange to widen into something larger.
Control slips when an organisation arrives at the window with no measured position, accepts vendor tooling as the only path, and lets the timeline run against it. Under pressure, teams declare numbers they cannot fully evidence, or they expose environments the certification did not require. The fix is time. A runway of around 18 months before the window gives room to measure, evidence, and reconcile without conceding ground.
To understand the whole exit, start with our Oracle ULA certification guide. To know who puts their name to the declaration, read who signs the certification letter and why. And if your count surfaces deployments that sit outside the agreement, read handling deployments found outside scope.
Certification is not an audit. It is your declaration of deployed quantities under the agreement. A clean, well evidenced certification does not invite an audit, though Oracle may review the declaration. The risk rises when the count is thin or unsupported.
Running Oracle LMS scripts is a choice, not an obligation, unless your contract states otherwise. You can build the count from your own tooling and records. The decision to run vendor scripts deserves analysis, because it shapes what Oracle sees.
We prepare the count and the evidence so your certification is a finished declaration, not an opening for scrutiny.