What records does OpenText copy in an Exstream audit

When an Exstream audit opens, one of the first practical questions a buyer faces is what the vendor is actually entitled to take. OpenText gives seven days notice before an audit and the right to copy relevant records, and how that right is exercised shapes the finding before any number is calculated. Knowing what records OpenText copies in an Exstream audit, and which of them carry the volume argument, lets a buyer control the production rather than hand over a raw export that becomes the baseline.

This article explains the record categories that matter, what the seven day notice triggers, and how a buyer manages the production through a single controlled channel. It supports our Exstream and customer communications audit defense practice and links up to the complete OpenText audit defense playbook for 2026.

The seven day notice and the right to copy

The contractual position is straightforward. OpenText runs a global software compliance team with executive sponsorship, and a Compliance Manager prepares the entitlement and support review before any true up negotiation begins. The EULA places the right to give seven days notice and to copy relevant records with the vendor, and it places the responsibility for compliance squarely on the licensee. Those two facts together mean a buyer cannot refuse the production, but it can and should control its form. The first seven days, the Respond phase of our method, are where that control is established. The cross cutting mechanics are set out in how OpenText measures Exstream usage in an audit.

The records that actually matter

An Exstream finding is built from volume, and the records that decide volume are narrower than a broad request implies. The categories that carry the argument are these:

• Composition logs. The record of how many documents the engine assembled, which the volume metric usually intends to charge.
• Job and batch records. Which runs were production and which were test, the basis for the non production scope in Exstream non production and test volume scope.
• Output and distribution logs. How a single composition fanned out into print, archive, and digital channels.
• Entitlement and authorization documents. The Additional License Authorizations that define the metric and the licensed quantities.

A finding cannot be larger than what these records support. When the production is controlled so that compositions are visible as distinct from renderings, the records themselves carry the reduction, as we describe in reducing an Exstream finding with volume evidence.

Why an uncontrolled production inflates the finding

The risk in handing over a raw output total is that it becomes the agreed baseline. If the vendor receives a single number for total output events, it can apply the most expensive metric reading to that number and present it as measured fact. Reconstructing a composed count afterward is harder than producing it correctly in the first place. The same applies to capacity and transactional records, where the distinction matters, as treated in Exstream transactional versus capacity metrics, and to API and batch activity, covered in how Exstream API and batch jobs are counted.

Controlling the production

Control is procedural, not obstructive. The buyer routes every request and every export through one channel, scopes each request to the records that are genuinely relevant, and produces composition logs in a form that preserves the distinction between a composed document and its renderings. Where a request is broader than the audit needs, the buyer narrows it to relevant records rather than refusing it. This keeps the vendor within its contractual right while ensuring the records that arrive support an accurate count rather than an inflated one. Building this control is part of reconciling Exstream entitlements before an audit.

A representative outcome

In a recent engagement, an early and uncontrolled export of total output events had set an inflated expectation before the defense began. By rebuilding the composition logs into a documented composed count and producing them through a single controlled channel, we replaced the raw total with an evidenced figure that distinguished compositions from renderings and test runs. The finding settled far below the opening expectation, in line with the reductions the firm achieves, where the average finding has come down 68 percent across more than 200 defended audits since 2020.

What this means for the first week

The records question is really a timing question. The seven day notice starts a clock, and the production decisions made in that first week determine whether the finding is built on a controlled, accurate record or on a raw total that overstates the volume. A buyer that treats the notice as the moment to establish a single controlled channel, rather than as a deadline to comply with quickly, protects every argument that follows. For the channel counting that often follows the records production, see Exstream output channel counting traps.

Relevance is a boundary, not a courtesy

The phrase that governs the production is relevant records. A request that reaches beyond what the audit needs is not automatically something a buyer must satisfy, and treating relevance as a real boundary rather than a polite formality is part of controlling the process. A broad request for all output data across every environment and every period is wider than an entitlement question requires. The buyer can narrow it to the records that bear on the metric and the audit window, produce those in a form that preserves the composition distinction, and document why the narrower set is the relevant one. This is not obstruction, because the vendor still receives the records that answer the compliance question. It is precision, and precision protects the buyer from a raw and over broad export becoming the agreed baseline. The compliance team is entitled to prepare its entitlement and support review, and the buyer is entitled to ensure that review rests on records that show compositions distinct from renderings and production distinct from test. Holding that boundary calmly, through one controlled channel, is what keeps the seven day notice from turning into an uncontrolled data handover. The same discipline carries into the capacity question treated in Exstream transactional versus capacity metrics.

None of this is adversarial toward the audit itself. The buyer that controls the production cooperates fully, produces the relevant records promptly, and simply ensures those records arrive in a form that tells the truth about composed volume rather than one that overstates it. That combination of cooperation and precision is what makes a controlled production both compliant and protective, and it is the posture we maintain from the first day of the seven day window through to resolution.