How Exstream volume metrics inflate an audit finding

Customer communications software is measured differently from the products buyers usually think of when they hear the word audit. There is no seat to count in the familiar sense. Instead the licensed quantity is volume: documents produced, pages rendered, output streams generated. When a finding builds on volume, the number can climb fast, because a single high traffic period or a generous definition of what counts as a chargeable unit can multiply the total well beyond what the buyer genuinely consumed. Understanding how Exstream volume metrics inflate an audit finding is the first step to holding a customer communications finding to a defensible figure.

This article explains how volume metrics work, where they overstate consumption, and how a buyer establishes the real number. It supports our Exstream and customer communications audit defense practice and links up to the complete OpenText audit defense playbook for 2026.

Why Exstream is a volume measurement

Exstream exists to generate customer communications at scale: statements, policies, notices, and correspondence produced across print and digital channels. Because the value is in output, the licensing tends to follow output, and the metric is some measure of volume rather than a count of users. That makes the volume figure the entire finding. There is no separate seat layer to fall back on, so whatever the measurement says the buyer produced becomes the basis for the deemed acquisition at list price, the back maintenance, and the forward proposal. The structure of these metrics is examined in what is an Exstream volume based license metric.

Where volume metrics overstate consumption

The recurring inflation points in an Exstream volume finding are consistent across engagements:

• Counting every output channel separately. One communication rendered to print, email, and archive can be counted three times rather than once, the subject of Exstream output channel counting traps.
• Counting pages where the unit is documents. A multi page statement inflates the total when the chargeable unit is the document, not the page, examined in Exstream document overcharge in a compliance review.
• Reading a peak period as the normal volume. A billing cycle or seasonal surge sampled as the typical month overstates the sustained figure.
• Folding non production and test runs into the count. Development and test output treated as production communications, the subject of Exstream non production and test volume scope.

Reading the metric against the contract

The defensible volume is the quantity the contract actually licenses, counted as the contract actually defines it. That means establishing what a chargeable unit is, whether it is a document or a page or an output stream, and whether multichannel delivery of one communication counts once or many times. A finding that applies the broadest possible reading of the unit is making a choice, not stating a fact, and the buyer holds the measurement to the definition written in the agreement. The wider measurement frame is set out in how OpenText measures Exstream usage in an audit.

Evidencing the real volume

The buyer reconstructs the genuine volume from its own production records: output logs, job histories, channel configurations, and the mapping of communications to chargeable units under the contract's definition. From these records it shows what was actually produced, removes duplicate channel counts, separates pages from documents where the metric calls for it, and scopes out non production runs. The reconstruction converts an undifferentiated output total into a contract scoped figure, and the defensible number is materially smaller. This is the same discipline described in reconciling Exstream entitlements before an audit.

How the four Rs take the volume down

The volume question runs through the method end to end. In the respond stage the firm takes over the single controlled channel so no raw output data reaches the vendor before the position is built, with the seven day notice clock starting immediately. In the reconstruct stage it rebuilds the genuine production volume against the contract's unit definition, independently and before any vendor measurement script runs. In the rebut stage every line of the volume calculation is challenged: the unit, the channel counting, the window, and the inclusion of non production runs. In the resolve stage the settlement is struck on the defensible volume and converted forward into an agreement whose metric is defined so the next measurement cannot drift upward. The earlier the production records are reconstructed, the cleaner the volume figure.

A representative outcome

In a recent engagement, an Exstream finding presented a volume figure that counted each communication once per output channel and treated a heavy billing month as the typical period. By reconstructing the production logs, collapsing the multichannel duplicates to single communications, and establishing the sustained monthly volume across a representative span, the buyer showed that the genuine licensed volume was a fraction of the figure claimed. The matter settled well below its opening number, consistent with the reductions we see across customer communications matters, where the firm has averaged a 68 percent reduction in the initial compliance finding across more than 200 audits defended.

The volume discipline in one line

Hold the volume to the contract's unit definition, count each communication once, scope out non production, and read the sustained period rather than the peak. That is how a buyer stops an Exstream volume metric from inflating the finding. For the line by line method that produces this result, see defending an Exstream volume overclaim line by line, and to put your production records to work you can open a case with our team.

For the first week after a notice arrives, read the OpenText seven day notice response white paper.