Why compliance is the sole responsibility of the licensee.

One short clause in the OpenText EULA shapes the entire balance of an audit: compliance is the sole responsibility of the licensee. It sounds procedural, but it sets who has to prove what, and that allocation of burden is the quiet force behind every aggressive finding. Understanding it is how a buyer turns a disadvantage into a discipline.

In most commercial disputes, the party making a claim has to prove it. Software licensing inverts that intuition. By placing the responsibility for compliance squarely on the licensee, the OpenText agreement means it is not enough to point out that the vendor has not proven overuse. You are expected to be able to demonstrate that your deployment matches your entitlements. When you cannot, the gap is read against you, and the deemed acquisition remedy fills it at list price.

What the clause actually says

The substance is simple. The EULA treats the licensee as the party responsible for ensuring that use stays within the granted rights. The vendor reserves the right to verify, but the obligation to be, and to be able to show that you are, compliant rests with you. This is why an audit does not feel like an investigation the vendor must win. It feels like an examination you must pass, and the questions are set in the vendor's preferred terms unless you reframe them.

This allocation is what makes the vendor's process effective even when its measurement is questionable. A self assessment script or a broad export produces a number, and because you carry the burden, that number becomes the default unless you can produce a better substantiated one. That is precisely why you should never let the vendor's measurement define the baseline, a point developed in building an effective license position before the vendor script runs.

Why the burden makes findings aggressive

The compliance clause is the reason auditors can open with expansive interpretations and broad data requests. They are not obliged to prove that every dormant account is a consumer or that every environment is production. They can assert it, count it, and price it, and then leave it to you to demonstrate otherwise. Each ambiguous population the vendor includes is a place where the burden works in its favour: silence reads as concession, and an unanswered count stands.

This dynamic is most visible in the categories that recur across every product line. Service and dormant accounts, read only users, non production and disaster recovery environments, and decommissioned systems all sit in the gap between deployment and entitlement, and the burden means each of them counts against you until you show it should not. Indirect and non human access is the same problem in another form, examined in indirect access in OpenText and Micro Focus audits. The vendor's organisation is built to exploit exactly this allocation, as described in inside the OpenText global software compliance team.

Carrying the burden is a discipline

If the burden is yours, the response is to carry it well rather than resent it. Carrying it means being able to produce a clear, evidenced account of your entitlements and your actual use, mapped to the defined license metric, before the vendor's number sets the frame. It means treating the agreement and the Additional License Authorizations as the governing text and reading your deployment against them, not against the auditor's characterisation. And it means holding back ambiguous populations for analysis rather than surrendering them, because the burden cuts both ways: a population you can substantiate as outside the metric is a population the vendor cannot simply count.

Done properly, the burden becomes leverage. The same clause that lets the vendor assert also lets you, once you can demonstrate your position, insist that the finding conform to the evidence rather than to assertion. The work of reconstructing entitlements so that the burden is met is the heart of the method and overlaps directly with our Micro Focus ALA and entitlement review.

Evidence beats assertion

Because the standard is what you can demonstrate, evidence is the currency of the defense. Usage logs that show which accounts were actually active, configuration records that distinguish production from test, decommissioning records that prove a system was retired, and the order forms and authorizations that fix your true entitlement are each more powerful than any argument made in the abstract. In a recent engagement the entire reduction turned on the ability to show, with dated usage evidence, that a large block of named accounts had never logged in, converting them from counted consumers into demonstrable non users. The burden was met, and the count fell.

This is also why preserving the estate at the moment a notice arrives matters so much. Deleting accounts or decommissioning systems after the notice destroys the very evidence you need to carry the burden and can look like spoliation. The disciplined alternative is to preserve, document, and argue analytically, which is part of what to do in the first 48 hours after an audit notice.

The burden through to settlement

The compliance clause does not relax during negotiation. The settlement reflects the position you were able to substantiate, which means the evidence you assembled to carry the burden is the same evidence that anchors the number you pay. A defense that meets the burden early enters the negotiation with a credible, documented counter position rather than a denial, and that is what converts an aggressive opening finding into a settlement on the buyer's terms. How that evidence drives the closing discussion is set out in true up negotiation tactics under audit pressure.

The clause is the whole game

Compliance being the sole responsibility of the licensee is not a detail to be argued away. It is the structural fact that explains why audits are framed in the vendor's terms and why unanswered counts become bills. The buyer side response is not to contest the clause but to honour it deliberately: reconstruct entitlements, evidence actual use, and carry the burden so completely that the finding has to conform to the facts. For the full method across every OpenText and Micro Focus product line, see the complete OpenText audit defense playbook. If a notice has arrived and the burden feels stacked against you, open a case and let an experienced team assemble the evidence that meets it.