Most Oracle ULAs require notice when control changes, and the notice you give shapes the position you negotiate from at exit. Disclose what the clause requires, accurately and on time, but say no more than it asks, because every extra word can open a scope question you did not need to raise.
Corporate change is a contractual event before it is a licensing one. A merger, an acquisition, or an internal restructure can trigger an obligation buried in the ULA to tell Oracle what happened, and the way that obligation is met can either preserve your leverage or quietly hand it away. The notice is not a formality. It is the moment Oracle learns the shape of your business has shifted, and a vague or premature disclosure invites questions that a precise one would have closed. This article sets out what triggers the duty, when it falls due, and how to disclose without surrendering ground. As always the controlling text is your own agreement, so use this to know what to look for and confirm the detail against the clause in front of you.
Usually yes, where the agreement contains a change of control or assignment clause that requires notice, which most ULAs do in some form. The trigger varies: some clauses fire on any change of control, some only when a defined ownership threshold is crossed, and some tie the duty to assignment of the agreement rather than ownership of the entity. The deadline, the recipient, and the required form are equally contract specific. The practical risk runs both ways. Failing to give a required notice can hand Oracle an argument that you breached the agreement, which is unhelpful leverage to concede before a certification. Disclosing more than the clause demands can invite Oracle to probe scope, entities, and deployments it had no standing to ask about. The discipline is to give exactly what the clause requires, no less and no more.
A notice clause is a one way window. Open it exactly as wide as the contract says, on the date the contract says, and let Oracle see only what it is entitled to see.
The deadline is whatever your agreement states, and it is commonly tied to completion of the transaction rather than its announcement. A ULA might require notice within a fixed number of days of close, at the next certification event, or promptly upon the change taking effect. The word promptly is doing real work in many contracts and is worth pinning down with advice rather than guessing. The safest practice is to identify the trigger and the clock the moment the deal is signed, diarise the deadline against the completion date, and prepare the notice in draft well before it is due. Notices given late, or given in a panic on the deadline, tend to say too much. Notices prepared early are the ones that say exactly enough.
| Clause type | What to confirm in your contract |
|---|---|
| Change of control | The ownership threshold that triggers it and the date the clock starts |
| Assignment | Whether the change counts as an assignment needing consent, not just notice |
| Customer definition | Whether the new entity falls inside or outside the defined customer group |
| Notice mechanics | The recipient, the form, the deadline, and what facts must be stated |
Triggers and deadlines are indicative and depend on your contract language.
Only what the clause requires, stated accurately and framed against the customer definition. In most cases that means the fact of the change, the entities involved, and the effective date. It does not mean a tour of your Oracle estate, a forecast of future deployment, or your reading of how scope now applies. Each of those volunteers information Oracle can use to widen the conversation, and none of it is usually required by the notice clause itself. Accuracy matters as much as restraint: a notice that misstates the entities or the date can be worse than a late one. The goal is a short, correct, contractually sufficient statement that closes the obligation and opens nothing else. Where the change interacts with an upcoming certification, the notice and the certification strategy should be drafted together so the two do not contradict each other.
Notice and certification are points on the same timeline, and what you say in one is read against what you claim in the other. If a notice describes the business one way and the certification letter counts deployments another way, the gap is exactly the kind of inconsistency an audit team looks for. The way to avoid it is to treat corporate change, disclosure, and certification as one connected workstream rather than three separate filings. The entities you name in the notice should match the entities whose deployments you certify. The effective dates should reconcile. The story Oracle assembles from your filings should be coherent and in your favour. That coherence is not luck. It is the product of preparing the notice with the exit already in view.
Disclosure is the visible half of managing corporate change against the ULA clock; scope is the half underneath it. Read divestitures during the ULA term for how a sale moves deployments outside scope, and the M&A clause language that protects you for the wording that makes notice straightforward rather than dangerous. For the full exit picture, read the ULA exit strategy guide.
Usually yes, where the agreement contains a change of control or assignment clause that requires notice. The exact trigger, the deadline, and the form of notice are set by your contract, so read those terms before the deal completes. Missing a required notice can hand Oracle an argument at exit, and over disclosing can invite scope questions you did not need to raise.
The deadline is whatever your agreement states, commonly tied to completion of the transaction rather than its announcement. Some ULAs require notice within a set number of days of close, others on the next certification. Because the clock and the trigger are contract specific, confirm both against your own terms and diarise the deadline as soon as the deal is signed.
Only what the clause requires, stated accurately and no more. That usually means the fact of the change, the entities involved, and the effective date, framed against the customer definition. Volunteering deployment detail, future plans, or interpretations of scope can create exposure. Disclose the required facts, keep the wording precise, and align the notice with your certification strategy.
Book a confidential assessment and we will read your notice clauses, draft a disclosure that meets them, and keep your leverage intact through certification.