COBOL & Mainframe · Track 07

Reconciling COBOL entitlements before an audit

The moment a COBOL audit notice lands, the vendor begins assembling its own version of what you are entitled to and what you are running. Reconciling COBOL entitlements before an audit means building your own version first, independently, so that when the vendor measurement script runs there is already a defensible position on the table rather than a blank one.

Visual COBOL and Enterprise Server reached the OpenText estate through the Micro Focus acquisition that closed on January 31, 2023, and both are governed by the Additional License Authorizations rather than the OpenText EULA. That distinction matters from the first day of a reconciliation, because the ALA, not a sales summary or a renewal quote, defines the metric that each product is counted on. A reconciliation that starts from anything other than the governing authorization starts from the vendor's framing, and the vendor's framing is exactly what produces the inflated opening finding. The work described here is the Reconstruct phase of the four Rs applied to a COBOL estate, and it is the phase that does the most to bring the number down.

Why reconciliation has to come before the script

Under the OpenText terms a licensee receives seven days notice before an audit and the vendor has the right to copy relevant records. That window is short, and the temptation is to let the vendor run its measurement first and respond to whatever it produces. Reconciling COBOL entitlements before an audit reverses that order on purpose. When you reconstruct the effective license position yourself, against your own entitlements and the authorizations that govern them, you arrive at the measurement with a number you can defend rather than a number you have to explain. The vendor script then has to be reconciled against your position, not the other way around. This is the same discipline set out across the COBOL cluster, including in how OpenText measures COBOL usage in an audit, and it is the single most effective protection against an opening finding that bears no relationship to the real deployment.

The mechanic

A finding is only as strong as the baseline it is measured against. If the vendor sets that baseline, every gap is yours to disprove. If you set it first, every gap is the vendor's to justify. Reconciliation is how the buyer takes control of the baseline.

What a COBOL reconciliation actually contains

A complete reconciliation pulls together three things and reconciles them against each other: what you are entitled to, what is governed by which authorization, and what is actually deployed. Each one is a distinct piece of work.

The entitlement record. Every Visual COBOL and Enterprise Server license you hold, with its quantity, its metric, and whether it is perpetual or term. This is read from the authorizations, not from a renewal invoice.
The metric map. Which products are counted by developer and which by capacity, a separation examined in Visual COBOL versus Enterprise Server licensing, so that no install is counted under the wrong metric.
The deployment inventory. Every install, host, and environment, classified as development or runtime, production or non production, live or decommissioned.

The reconciliation is the act of laying these three against one another and resolving every discrepancy before the vendor sees any of it. Where deployment exceeds entitlement, the question is whether the excess is real or an artefact of how it was counted. Where entitlement exceeds deployment, that headroom is a credit the vendor will not volunteer.

The discrepancies that surface first

In practice the same categories of discrepancy appear in almost every COBOL reconciliation, and naming them in advance speeds the work. Development installs of Visual COBOL get counted as if they were runtime deployments. Non production Enterprise Server environments get priced at production capacity, a scoping question covered in COBOL non production and test environment scope. Decommissioned workloads remain on an inventory that was never cleaned, a problem examined in decommissioned COBOL workloads still on the audit. Cores get counted on physical capacity when the workload runs on a constrained subset. Each of these is a discrepancy that a reconciliation done early can resolve with evidence, and that a reconciliation done late has to argue under pressure.

Holding the reconciliation against the vendor measurement

The point of reconciling COBOL entitlements before an audit is not to predict the vendor number exactly but to be ready to hold a defensible position against it. When the vendor measurement arrives, every line is compared to the reconciliation. Lines that match are conceded quickly, which builds credibility. Lines that diverge are challenged with the evidence already assembled: the metric map shows the count is on the wrong basis, the deployment inventory shows the host is non production or decommissioned, the entitlement record shows headroom the vendor ignored. This is the Rebut phase, and it is far stronger when the reconstruction behind it was done first. Challenging a single core measurement in isolation is harder than challenging it from a complete, independent baseline, as set out in how to challenge a COBOL core measurement.

In a recent engagement

In a recent COBOL engagement, the reconciliation was built during the seven day notice window before the vendor measurement script was permitted to run. It revealed three things the opening finding would later get wrong: a block of Visual COBOL development installs counted as runtime, an Enterprise Server test environment scoped at production capacity, and a set of decommissioned workloads still carried on an old inventory. Because the reconciliation existed first, each of those lines was contested on day one of the rebuttal rather than discovered weeks into it. The baseline belonged to the buyer, and the burden of justifying every divergence sat with the vendor. The reduction came not from a single clever argument but from having done the reconciliation before, rather than after, the measurement.

Building the reconciliation under time pressure

The seven day clock is the real constraint, and a reconciliation has to be built to fit it. The priority order is to secure the authorizations and entitlement record first, because everything else is measured against them, then to map the metrics, then to inventory the deployment by environment. Even a partial reconciliation completed inside the notice window changes the dynamic of the audit, because it establishes that the buyer has an independent position. The reconciliation is then refined through the Reconstruct phase as more evidence is gathered, but the framing is set early. A buyer who waits until the finding arrives to begin reconciling is always reacting; a buyer who reconciles first is setting the terms. The broader sequence is laid out in the complete OpenText audit defense playbook for 2026.

Has a COBOL notice arrived before you have reconciled your own position?

We build the independent Visual COBOL and Enterprise Server entitlement position before any vendor script runs, so the baseline is yours. To get a defense team on the file, open a case or download the guide to reading the Micro Focus ALAs.

Get The Number Down →

Related field notes

These notes from the COBOL and Enterprise Server mainframe audit defense cluster cover entitlement, metrics, and scope. Each links back to the complete OpenText audit defense playbook for 2026.

If an OpenText or Micro Focus audit notice has arrived, the first seven days carry more weight than any week that comes after. OpenText Audit Defense is an independent, buyer side practice founded in 2020 by former vendor compliance leadership. We have defended more than 200 audits, cut the average finding by 68 percent, and mitigated more than $90M in claims against vendor positions. We do not resell OpenText software and we are not affiliated with OpenText Corporation. To open a case, use the contact form on this site.