How to reconcile Documentum entitlements before an audit

The single most valuable thing a Documentum customer can do is reconcile its entitlements before an audit forces the question. When you know exactly what you own, a finding starts from your numbers rather than the vendor's, and the whole negotiation shifts in your favour.

An audit baseline is built by the party that benefits from it being incomplete. Because the OpenText EULA makes compliance the sole responsibility of the licensee, the burden of proving what you hold rests with you, and an audit that begins with an underdocumented entitlement position produces a finding that overstates the shortfall. Reconciling entitlements ahead of time inverts that dynamic. Instead of arguing down from a number the vendor produced, you arrive with a defensible position already assembled. This is the Reconstruct phase of our method done in advance, and it is the most cost effective audit preparation there is.

Why reconcile Documentum entitlements before the notice arrives

OpenText gives seven days notice before an audit and the right to copy relevant records. Seven days is not enough time to locate decade old purchase records, untangle which licenses are perpetual and which are term, and separate live users from dormant accounts. A customer who begins that work only when the notice arrives is permanently on the back foot. A customer who has already done it meets the audit with a complete entitlement picture and treats the exercise as a comparison rather than an investigation.

The advantage compounds. A reconciled entitlement position lets you spot overuse before the vendor does and address it on your own terms, identify entitlements the vendor may have overlooked, and refuse to accept an inflated baseline. It also transforms the tone of the engagement, because a customer who clearly knows its own position is a far less attractive target than one scrambling to respond. The reconciliation itself follows the discipline we set out in preparing a Documentum entitlement reconstruction.

The steps to reconcile Documentum entitlements

Assemble the entitlement record

Start with every source of entitlement: original purchase orders, license certificates, contract amendments, and maintenance renewals. Documentum estates accumulate over many years, so this record is often scattered across systems and predecessors. Building a complete entitlement record is the foundation, and gaps in it are exactly what an audit exploits. The distinction between perpetual and term licenses matters here, as we explain in Documentum perpetual versus term license positions.

Map the deployed estate

Next, establish what is actually deployed: which repositories, servers, and clients exist, and which are production, non production, decommissioned, or held for disaster recovery. The deployed estate is what the audit will measure, and you need your own accurate map of it before the vendor produces theirs.

Reconcile users against the metric

Compare the user population to the licensed metric. Separate live users from dormant accounts, lift out service and integration identities, and classify read only and occasional users against the metric definition. The undifferentiated account list that an audit prefers is not a license position, and reconciling it to genuine, entitled users is where much of the protection comes from. The pattern is the one we describe in how Documentum named user counts inflate an audit finding.

Identify and document gaps

Where the reconciliation reveals genuine overuse, document it and decide how to address it on your own timetable rather than under audit pressure. Where it reveals entitlements the records support but the deployed estate does not fully use, note them as credit. Either way, you now hold a complete picture rather than a surprise.

Turning the reconciliation into a defense under the four Rs

Respond. With a reconciled position already in hand, the seven day window becomes manageable. We take over the channel and present a controlled, accurate entitlement picture rather than allowing a raw export to define the baseline.

Reconstruct. The heavy lifting is already done. The pre audit reconciliation is the reconstruction, and it means the effective license position is established before any vendor measurement script runs, exactly as our method intends.

Rebut. Every line of the finding is tested against the reconciled position. Undercounted entitlements are restored, miscounted users are corrected, and non production and decommissioned systems are scoped out, all from documentation already assembled.

Resolve. We settle on the reconciled, corrected position and, where it serves you, convert forward into an OpenPass agreement that records the entitlements clearly, so the next audit starts from an agreed baseline rather than an open question.

An anonymised outcome

The value of reconciling first shows up directly in the result. 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, so every overstated line in the baseline multiplies. 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, because the genuine entitlement and user position was reconstructed and held against the vendor's inflated starting figure. A customer who reconciles before the audit captures that advantage from day one rather than recovering it under pressure.

Reconciliation as a standing discipline

The deeper lesson is that entitlement reconciliation is not a one time fire drill but a discipline worth maintaining. A Documentum estate changes constantly as users join and leave, repositories are created and retired, and contracts are renewed and amended. An entitlement position that was accurate two years ago may be stale today. The customer that keeps its reconciliation current treats every potential audit as a comparison against a known position, and never again faces the seven day scramble.

Maintaining the reconciliation also surfaces problems early, when they are cheap to fix. Overuse caught internally can be addressed through ordinary procurement on the customer's timetable, rather than through a deemed acquisition at list price under audit pressure. Entitlements that go unused can inform renewal decisions. In short, the same work that defends an audit also improves ordinary license management, which makes it worth doing whether or not a notice ever arrives.

For the buyer, the practical takeaway is simple. The audit is a question about what you own and what you use, and the customer that can answer that question from its own records, before the vendor asks it, holds the stronger position by a wide margin. Reconcile first, and the finding becomes a negotiation over facts you already control.

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. To carry the reconciliation into a formal rebuttal, read how to document Documentum named users for a rebuttal. If a Documentum notice has already arrived and you have no reconciled position yet, open a case and we will build one inside the seven day window.