Reconciling ALM entitlements before an audit

Reconciling ALM entitlements before an audit is the single most valuable thing a buyer can do, because the reconciliation builds the verified license position that every later argument rests on. Done well, before any vendor count exists to react to, it turns the audit from a defensive scramble into a negotiation conducted from a position you control.

Most organisations discover their Application Lifecycle Management entitlements are scattered: original order forms, later amendments, migration paperwork, and renewal records held in different places by different teams, none of them reconciled against the deployment that actually exists today. When an audit arrives, that scatter becomes a liability, because the vendor produces a count from the live system and the buyer has nothing verified to set against it. Reconciliation closes that gap in advance. Since the EULA places compliance on the licensee, the buyer is expected to know its own position, and building that position before the notice lands is both the obligation and the advantage. OpenText gives seven days notice before an audit, which is rarely enough time to reconcile from scratch, so the work is best done ahead of any trigger.

What reconciling ALM entitlements actually involves

Reconciliation is the disciplined matching of three things: what you are entitled to, what is deployed, and how each license is metered. The entitlement side means assembling every order form and amendment into a single authoritative record of how many licenses of each product and edition you hold, and crucially under which model, named or concurrent, since that distinction governs everything that follows, as set out in named versus concurrent user counting in ALM audits. The deployment side means a clean inventory of users, projects, and environments, deduplicated and stripped of dormant and departed accounts. The metering side means confirming, for each license, what unit it counts, so the deployment can be measured against the entitlement on the same terms the contract uses.

The output is a reconciliation that shows, product by product, whether you are within entitlement, and if not, by exactly how much and why. That document is the foundation of the defense, because it lets you meet any vendor count with a verified figure of your own rather than improvising under time pressure.

Where reconciliation removes inflation before the count

Dormant and departed accounts

Reconciliation strips accounts with no activity from the deployment inventory before they ever reach a finding, the same evidence based removal applied in documenting concurrent ALM users for a rebuttal.

Retired projects and environments

Decommissioned projects and non production environments should not carry live licensing, and a reconciliation identifies them in advance, the questions examined in decommissioned ALM projects still on the audit and LoadRunner non production and test environment scope.

Model mismatches

Confirming named against concurrent for each license, ahead of the audit, prevents the largest single category of overcharge from ever taking hold, the distinction at the heart of named versus concurrent user counting in ALM audits.

How we reconcile under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. Where a notice has already arrived, we take over the single controlled channel immediately and begin the reconciliation against the clock; where it has not, we do the work in calm conditions so nothing is improvised later.

Reconstruct. This is the heart of reconciliation: we build the effective license position from entitlements and the Additional License Authorizations, matching deployment to contract on the correct metric, before any vendor measurement script runs.

Rebut. With a verified position in hand, every line of a vendor finding can be tested against it, and the differences resolved with evidence rather than assertion.

Resolve. We settle on the reconciled figure and, where it serves you, convert forward into an OpenPass agreement that records the reconciled position, so future reviews start from agreed ground.

An anonymised outcome

The reason reconciliation pays is the remedy it pre empts. 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 OpenText incurs performing the audit, so a reconciliation that removes inflation before the count begins removes the whole stack of charges those seats would have carried. Our anonymised case files show what disciplined reconstruction recovers, including an insurance ECM seat count finding reduced from $7.2M to $1.6M, a 78 percent reduction built on exactly this kind of groundwork. An ALM reconciliation works the same way: establish the verified position first, and the audit has far less room to inflate.

Do the work before the notice, not after

The lasting lesson is that reconciliation is most powerful when it is done in advance, because the seven day notice window leaves little room to build a verified position from nothing. A buyer who reconciles ahead of any trigger walks into the audit with its own authoritative figure and meets the vendor count from strength. To carry the work forward, see how the vendor assembles its numbers in how OpenText measures ALM in a self assessment and how the reconciled position supports defending an ALM named user overclaim line by line. For the full method see our ALM and LoadRunner audit defense track and our complete OpenText audit defense playbook for 2026. To begin reconciling before an audit reaches you, open a case.