Can OpenText count all output channels separately

One of the most expensive moves in an Exstream audit is the decision to treat each delivery channel as a separate chargeable event. A single customer communication that goes to print, to email, and to an archive can be counted once, or it can be counted three times, and the difference between those two readings is often the difference between a finding the buyer expected and one that triples it. The question buyers raise as soon as they see this happen is simple: can OpenText count all output channels separately, and is there anything in the contract that says it must be counted that way. The answer is that the contract decides, and the contract rarely says what the finding assumes.

This article explains how channel counting works, when separate counting is supportable and when it is not, and how a buyer reads the metric back to its contractual meaning. It supports our Exstream and customer communications audit defense practice and links up to the complete OpenText audit defense playbook for 2026.

What separate channel counting means

Customer communications software produces output that can be delivered through several channels: physical print, email, an online portal, an archived copy, and sometimes a mobile or interactive channel. When a finding counts channels separately, it treats each delivery of a communication as its own unit against the volume entitlement. A statement run that produces one logical document per customer, delivered to two channels each, is then counted as two units per customer rather than one. The volume base doubles before any other variable is applied, and because the remedy stacks off that base, the doubling carries through the entire finding. The broader pattern is set out in Exstream output channel counting traps.

When separate counting is supportable

Separate channel counting is not always wrong. If the contract defines the chargeable unit as an output transaction or a delivered communication per channel, then a communication sent to three channels genuinely consumes three units, and the finding is reading the metric correctly. The buyer's task in that case is not to deny the counting but to verify it: confirm the channel configuration, confirm that each counted delivery actually occurred, and confirm that the channels in question fall inside the licensed scope. Even where separate counting is contractually supported, the count is only as good as the evidence behind each delivery, which is why production logs matter as much as the contract language.

When separate counting is not supportable

Separate counting fails when the contract licenses the document or the communication rather than the delivery. If the chargeable unit is a composed document, then producing that document once and routing it to several channels is one unit, not several, because the licensed event is the composition rather than the delivery. A finding that nonetheless multiplies by channel has substituted a delivery count for a document count, and the buyer rebuts it by pointing to the unit the contract actually names. This is the same distinction that governs Exstream page and document counting explained, where the chargeable unit also turns on contract language rather than on what is easiest to measure.

How a buyer reads channels back to the contract

The defensible channel count is the one the agreement supports, evidenced from production records:

• Locate the unit definition. Find where the contract names the chargeable unit and whether channel is part of that definition or separate from it.
• Map the channel configuration. Establish how communications are actually routed and which deliveries occurred, from the system's own output logs.
• Separate composition from delivery. Distinguish the act of producing a communication from the act of delivering it, and count whichever the contract licenses.
• Scope the channels. Confirm which channels are inside the licensed scope and which, such as internal archival copies, should not count at all. The archival question is examined in CCM print stream and archival licensing.

The result is a channel count tied to the contract rather than to the broadest reading, which the buyer can defend line by line. The way the metric definition itself frames multichannel output is set out in Exstream multichannel output and the metric definition.

How the four Rs apply to channel counting

Channel counting runs through the method like any other volume variable. In the respond stage the firm takes over the single controlled channel inside the seven day notice window so the vendor does not set the channel reading before the position is built. In the reconstruct stage it rebuilds the genuine output against the contract's unit definition, separating composition from delivery and scoping each channel. In the rebut stage every instance of channel multiplication is tested against the contract, and any delivery counted as a chargeable unit without contractual support is removed. In the resolve stage the settlement reflects the defensible channel count, and the forward agreement defines the unit so that channel treatment cannot be reopened at the next measurement. The earlier the channel configuration is reconstructed from production logs, the more precisely the count can be defended.

A representative outcome

In a recent engagement, an Exstream finding had counted each delivery channel as a separate chargeable unit, so communications composed once and routed to print, email, and archive were counted three times against the volume entitlement. The buyer located the unit definition in the contract, which licensed the composed communication rather than the delivery, and reconstructed the channel configuration from the system's output logs. Once composition was separated from delivery and the archival copies were scoped out, the volume base fell to roughly a third of the claimed figure. The matter settled well below its opening number, consistent with the reductions the firm sees across customer communications matters, and no new figures were introduced to reach it.

The channel question in one line

OpenText can count output channels separately only where the contract licenses the delivery rather than the document, and a finding that multiplies by channel without that support is reading the metric for maximum value. Pin the unit to the agreement and the count returns to its defensible size. For the wider measurement picture, read how OpenText measures Exstream usage in an audit, and to have your own channel 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.