Exstream page and document counting explained

The single most consequential decision in an Exstream audit is what gets counted as a unit. A page is not a document, a document is not a communication, and a communication is not a delivery, yet a finding can quietly slide between these definitions to land on whichever produces the largest base. Because the volume base feeds the entire stacked remedy, an inflated unit definition at the bottom multiplies all the way to the top. Getting Exstream page and document counting right is therefore not a technical footnote. It is the foundation the whole finding stands on.

This article explains how pages, documents, and communications differ, where a finding inflates by choosing the wrong unit, and how a buyer reads the count back to the contract. It supports our Exstream and customer communications audit defense practice and links up to the complete OpenText audit defense playbook for 2026.

Pages, documents, and communications are not the same

A customer communications run produces a layered output. At the finest level are pages, the physical or logical sheets of a printed or rendered output. Above that are documents, the composed pieces that form a complete statement, letter, or notice. Above that are communications, the logical message to a customer that may comprise several documents. And above that are deliveries, the routing of a communication to one or more channels. A volume metric licenses one of these layers, and the gap between layers can be large: a single communication can contain several documents, each running to several pages. Which layer the contract charges is the question that decides the base. The way this drives the overall finding is set out in how Exstream volume metrics inflate an audit finding.

Where the count inflates

A finding inflates the count in a handful of recurring ways:

• Counting pages as the unit. Treating each page of a multi page document as a chargeable unit when the contract licenses documents.
• Counting components as documents. Treating each reusable component or insert within a document as its own document.
• Counting documents as communications. Treating each document within a multi document communication as a separate communication.
• Counting deliveries as communications. Multiplying by channel, the trap examined in Exstream output channel counting traps.

Each of these substitutes a lower, more numerous layer for the layer the contract actually names, and each inflates the base accordingly. The cumulative effect on what the buyer pays is set out in Exstream document overcharge in a compliance review.

How a buyer reads the count back to the contract

The defensible count is the one at the layer the contract licenses, evidenced from production records. The buyer locates the chargeable unit in the agreement, then reconstructs the genuine output at that layer from the system's own composition and output logs: how many communications were produced, how many documents each contained, and how many pages each document ran to. With those layers separated, the buyer counts only the layer the contract names and discards the inflation from lower layers. The practical version of this work, where a specific claimed count is contested, is set out in how to challenge an Exstream document count. The result is a base anchored to the contract rather than to the most numerous available reading.

How the four Rs apply to the count

The page and document count runs through the method as the first thing to establish. In the respond stage the firm takes over the single controlled channel inside the seven day notice window so the vendor does not fix the unit reading before the position is built. In the reconstruct stage it rebuilds the genuine output at every layer from production logs and identifies the layer the contract licenses. In the rebut stage every instance of counting at a lower layer than the contract names is challenged and removed. In the resolve stage the settlement reflects the count at the contractual layer, and the forward agreement defines the unit so the next measurement cannot drift between layers. The earlier the layered output is reconstructed, the harder the count is to inflate.

A representative outcome

In a recent engagement, an Exstream finding had counted at the page layer while the contract licensed composed documents, so a portfolio of multi page statements had been counted at several times its document volume. The buyer located the chargeable unit in the agreement, reconstructed the layered output from the system's composition logs, and showed that the genuine document count was a fraction of the page count the finding had used. Once the base was reset to the contractual layer, the stacked remedy fell with it. The matter settled well below its opening number, consistent with the reductions the firm sees across customer communications matters, with no figure introduced beyond what the production logs contained.

Page and document counting in one line

Exstream output is layered into pages, documents, communications, and deliveries, and the finding must count at the layer the contract licenses rather than the most numerous one available. Reconstruct the layers, anchor the unit to the agreement, and the base returns to its defensible size. For the broader measurement frame, read how OpenText measures Exstream usage in an audit, and to have your own count read against the contract 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.