Full narration of the briefing. Click a section heading to jump the player to that moment.
The certification window is short. Typically thirty to ninety days around your term end, depending on what your agreement says. Inside it you declare what you deployed, Oracle reviews it, and the agreed number becomes your permanent perpetual entitlement. What makes this window difficult is not its length.
It is that almost nothing about the count can be changed once you are inside it. I am Daniel, Claire is with me, and this session is what actually happens in those weeks and how to arrive in a position to defend your number rather than discover it.
What you submit is a declaration of deployed quantities, product by product, usually signed by a company officer. That signature matters, because you are formally certifying accuracy rather than sending an estimate. Behind the declaration sits your supporting material: the inventory, the environment list, the evidence. Oracle does not simply accept the number and file it.
They review it against what they know about your estate, which includes your purchase history, your support records, previous audits, and anything your teams have told their teams over three years of ordinary conversation.
Their review looks at three things, and knowing them tells you how to prepare. Consistency: does the declared number make sense against your history, your support base and your known architecture. Scope: is everything claimed actually inside the contracted products, entities and territories, which is exactly the boundary work from session two. And plausibility: can you evidence it.
A large increase in the final months attracts attention, which is not a reason to avoid legitimate late deployment, but it is a very good reason to have contemporaneous records showing the work was real, funded and planned.
So what evidence actually holds? Three properties. Dated: it shows deployment existed before the freeze, not that it exists now. Contemporaneous: it was captured at the time rather than reconstructed afterwards from memory.
And independent where possible: configuration exports, monitoring data, change tickets, and asset records carry more weight than a spreadsheet assembled last week. The strongest position is a rolling inventory captured monthly through the final year, because it demonstrates a process rather than an effort, and a process is much harder to argue with.
Now the mistakes, because counts shrink for predictable reasons. First, environments omitted because someone assumed they did not count, particularly non production. Second, deployment that cannot be evidenced, so it gets withdrawn rather than defended. Third, claims outside contracted scope, which are removed and cost you credibility on everything else.
And fourth, an unstaffed process: the person who understood the estate left, and the submission gets built in a fortnight by whoever is available. Every one of those is a preparation failure rather than a negotiation failure, and every one is fixable a year earlier.
Running the window itself is mostly discipline. One named owner, so there is a single version of the count. One evidence file, indexed, so any challenged line can be substantiated within a day rather than a fortnight. Answer what is asked rather than volunteering the estate's history.
And expect challenge on the largest lines, because that is where the value is, so prepare those first and in the most depth. If you have done the twelve months properly, this period is administration. If you have not, it is a negotiation you are entering without preparation, against a counterparty who does this every week.
The move from this briefing: start capturing a dated inventory snapshot every month, from today until your window opens. It takes an hour a month and it is the difference between a count you can defend and a count you have to withdraw. Name the owner today too, because certifications fail on absent owners more often than on hard questions. Next session: renewing, for the organisations where another term genuinely is the right answer.
See you there.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a Oracle negotiator