Content Suite license metrics and where audits overcharge

Content Suite license metrics look simple on the order form and behave very differently under an audit. The gap between how the platform is licensed and how an audit chooses to measure it is exactly where the overcharge lives, and it is usually defensible once you understand the mechanics.

Content Suite is OpenText's own enterprise content management platform, and like the rest of the OpenText ECM line it predates the Micro Focus acquisition and is governed by the OpenText EULA rather than the Micro Focus Additional License Authorizations. That distinction matters, because the EULA places compliance squarely on the licensee and gives OpenText broad rights to measure. The practical consequence is that the way a Content Suite estate is counted at audit time often differs from the way it was bought, and the difference falls in the vendor's favour unless someone defends the count line by line.

What Content Suite license metrics actually measure

Content Suite is most often licensed on a user metric, but the word user hides several distinct populations. There are people who log in and work with content directly, people who only consume content through another application, accounts that exist for administration or integration, and accounts that were provisioned years ago and never decommissioned. A clean license position treats these populations differently. An audit, left to its own devices, tends to collapse them into a single large number.

The first task in any Content Suite defense is therefore to define the metric precisely against the entitlement documents, then to hold the audit to that definition. When the metric is a named user, the question is who genuinely holds a named entitlement. When it is a different unit, the question changes, but the discipline is the same: the contract defines the unit, and the count must follow the contract, not a convenient database query. The same metric discipline applies across the OpenText content portfolio, which is why it helps to read this alongside Content Server CPU and instance based metrics explained.

Where Content Suite audits overcharge

Inactive and dormant accounts counted as live users

The most common Content Suite overcharge is treating dormant accounts as chargeable users. Large content platforms accumulate accounts over years. People change roles, leave the organisation, or were provisioned for a project that ended. If the audit counts every account that still exists in the directory, the user number inflates well beyond the people who actually work with the platform. Usage evidence, not directory presence, should drive the count. The broader pattern is the same one we describe in how Documentum named user counts inflate an audit finding.

Service and administrative accounts treated as consumers

Content Suite runs on service identities for integration, indexing, and administration. These are infrastructure, not people, and they should not be counted as licensed users. Audits frequently sweep them into the user population because they appear in the same account tables. Separating them out is one of the cleanest reductions available in a Content Suite finding.

Module licensing applied to the whole platform

Content Suite is modular. Specific capabilities may be separately licensed, and a user entitled to the core platform is not automatically entitled to or consuming every module. An audit can overcharge by applying a module metric across the entire user base rather than to the users who actually touch that module. We set out the platform and module distinction in detail in Content Suite platform versus module licensing.

Indirect and integration users counted directly

When Content Suite is embedded in or connected to another business application, people who only reach content through that application can be counted as direct Content Suite users. Whether that attribution is fair depends on how the person actually interacts with content, the same indirect access question that runs through every ECM finding.

How we defend Content Suite license metrics under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. In that window we take over the channel so that a raw export of every Content Suite account does not silently become the agreed user count. Controlling what is measured, and how, begins on day one.

Reconstruct. We build the effective license position independently. We separate live users from dormant accounts, lift service and administrative identities out of the population, align each remaining user to the correct metric and module entitlement, and compare the result to what was actually purchased. This reconstruction is the foundation of every later argument, and the process mirrors the one in how to reconcile Documentum entitlements before an audit.

Rebut. We challenge every inflated line. Dormant accounts come out on usage evidence. Service accounts come out as infrastructure. Module charges are confined to actual module users. Indirect users are tested against how they really interact with content. Each contested item is supported by fact, not assertion.

Resolve. We settle on the corrected position and, where it serves you, convert forward into an OpenPass agreement with defined metrics and audit protections, so the same metric ambiguity cannot reopen at the next renewal.

An anonymised outcome

The leverage in a metric defense is large because the remedy multiplies the error. On noncompliance the licensee is deemed to have acquired licenses at then current list price, owes back maintenance and support, owes first year maintenance on the new licenses, and reimburses the cost of the audit itself. A count inflated by dormant and service accounts therefore inflates four times over. In our anonymised insurance engagement, case file E-01, a Documentum centred ECM finding fell from $7.2M to $1.6M, a 78 percent reduction, by holding the count to the people who genuinely held and used the entitlement. The same discipline applies directly to Content Suite license metrics.

Reading the metric before the audit reads it for you

The deeper point is that Content Suite license metrics are not self evident. The same platform can produce wildly different numbers depending on which accounts you include, which metric you apply, and whether you count module use across everyone or only across module users. Because the EULA makes compliance the sole responsibility of the licensee, the vendor has little incentive to read the metric in your favour. Reading it correctly, before the audit fixes its own reading in place, is the single most valuable thing a buyer can do.

That reading starts with the entitlement documents. Every defensible count traces back to what the contract actually grants, in the units the contract actually uses. From there it is a matter of evidence: which accounts are live, which are infrastructure, which users touch which modules, and which apparent users only reach content through another system. Assemble that evidence first and the audit becomes a negotiation over facts you already hold, rather than a scramble to disprove a number the vendor produced.

None of this requires accepting the vendor's framing. A Content Suite finding is a claim, not a settled fact, and a claim built on an undifferentiated account export is weak. The buyer who separates the populations, ties each to the correct metric, and documents usage holds the stronger position by a wide margin.

Where to go next

For the full method behind an ECM finding, read our complete OpenText audit defense playbook for 2026 and our ECM and Documentum audit defense track. It is also worth understanding how Content Suite compares to the wider platform in Extended ECM versus Documentum licensing differences. If a Content Suite finding has landed and the metric looks inflated, open a case and we will read the count back to what your contract actually grants.