Closing an Oracle ULA certification cleanly comes down to a short, disciplined list: confirm the count, sign and submit the letter on time, secure Oracle's confirmation of the entitlement, archive the evidence, and right size support. Each step protects the value you spent the engagement building.
By the Meridian advisory team, former Oracle LMS and GLAS licensing analysts. Updated 4 June 2026.
Closing a certification well is not complicated, but every step carries consequence because the event is irreversible. Confirm the count against the evidence file, secure the right executive signature on the certification letter, submit inside the contract window, retain Oracle's written confirmation of the perpetual entitlement, archive the full data room, and right size your support and monitoring for the estate you now hold. Miss any one and you risk either losing entitlement or leaving exposure behind. The checklist below is the order we work through with clients at the close of an engagement.
The certification is the one irreversible moment in the ULA lifecycle. Treat the close as a controlled sequence, not a final email, because everything you fail to lock down here is harder to recover later.
Before anything is signed, reconcile the number one last time against the data room. Every processor in the declared count should trace to an inventory line, a discovery record, and a contract mapping that places it in scope. This final pass catches the late discovery that adds entitlement and the out of scope deployment that would have created exposure. The number you sign should be the number you can prove, with nothing missing and nothing you cannot defend.
The certification letter typically requires a senior executive to sign, often at C level. Identify the correct signatory early, brief them on what the declaration means, and make sure the letter they sign reflects the reconciled count and the agreement's exact requirements. A signature from the wrong authority, or a letter that does not match the contract's wording, can put the whole certification in question. This is a step to confirm well before the deadline, not on the day.
The certification window is finite. Missing it can force a renewal you did not want and hand Oracle leverage you did not need to give. Confirm the deadline and any notice period in the certification clause, build in time for internal review and signature, and submit with margin. The clock is one of the few elements of the exit entirely within your control, so it should never be the thing that costs you the outcome.
After submission, Oracle confirms the certified quantities. Keep that confirmation in writing alongside the signed letter. Together they are your proof of perpetual entitlement, the document you will rely on for every future order, migration, and audit. An entitlement you cannot evidence is an entitlement you may have to argue for again, so this record is not administrative housekeeping. It is the title to what you captured.
Audit risk rises in the first two years after certification, and the evidence file behind your number is the defense. Archive the complete data room, the inventory, the discovery data, the processor calculations, the cloud and virtualization documentation, and the contract mapping, in a form your team can retrieve quickly. The discipline of building it before the certification, which we cover in preparing the certification data room, pays off here: the file that supported your count is the same file that defends it. The way Oracle tests that file is set out in how Oracle reviews a certification.
With the entitlement secured, turn to the estate you now hold. Confirm your support position, set up monitoring so future growth beyond the certified count is licensed deliberately rather than discovered in an audit, and document the perpetual entitlements by product. The aim is that a future migration, acquisition, or review never erodes the position you just secured. Certifying out is the win. Holding the win is the work that follows.
| Step | Action | What it protects |
|---|---|---|
| Confirm | Reconcile the count to the evidence | A defensible, complete number |
| Sign | Right executive, correct letter | A valid certification |
| Submit | Inside the contract window | Avoids a forced renewal |
| Retain | Oracle's written confirmation | Proof of perpetual entitlement |
| Archive | The full data room | Defense in the audit window |
| Right size | Support and monitoring | The position you captured |
The exact requirements at each step depend on your agreement, so confirm the signature authority, the deadline, and the confirmation process against your own contract wording.
A clean close turns a maximised count into a secured, defensible perpetual entitlement. Confirm, sign, submit, retain, archive, and right size, in that order, and the value you built through the engagement is locked in rather than left to chance. The full process sits in our pillar, the Oracle ULA certification guide. When you are ready to run the exit with that discipline behind you, we can help.
Confirm the count against the evidence file, secure the right executive signature on the certification letter, submit within the contract window, retain Oracle's confirmation of the perpetual entitlement, archive the full data room, and right size your support and monitoring for the post exit estate. Each step protects the value you just captured.
Keep the signed certification letter, Oracle's written confirmation of the certified quantities, and the complete evidence file behind the count. These are your proof of entitlement and your defense if an audit arrives in the first two years after certification, when audit risk is at its highest.
Book a confidential assessment and we will run the close with you, from the final count to the secured entitlement.