Reconciling entitlement to deployment.

Where measurement becomes a number you can sign

Measurement is not the same as a certified count

A deployment measurement tells you what is running. A certified count tells you what you are entitled to convert into perpetual licences. They are not the same thing, and the gap between them is reconciliation. A raw measurement includes everything discovery finds, some of which your contract counts and some of which it may not, because of where it sits, which entity owns it, or whether it falls inside the product and territory scope. Reconciliation is the work of mapping the measurement onto the agreement so that the number you declare reflects what you can actually claim and defend.

This distinction is why a count that looks finished after discovery is often not finished at all. Two instances of the same product can have opposite outcomes once reconciled, one counting toward entitlement and the other falling outside scope. Skipping reconciliation means certifying a measurement rather than a position, and a measurement does not know about your customer definition, your territory clause, or your evidence. The certified number must, because it becomes permanent and is the baseline an auditor will later test.

What does it mean to reconcile entitlement to deployment?

Reconciliation moves systematically from raw measurement to a defensible count through a series of tests. Each test either confirms a deployment belongs in the count or flags it for separate handling, and each leaves a documented basis behind it.

• Product scope. Confirm each deployment is one of the products named in the unlimited grant, since only those products certify.
• Customer definition. Check that the entity running each deployment falls within the customer definition, because instances owned by an out of scope entity may not count.
• Territory. Confirm the deployment runs within the territory the agreement covers, as geography can exclude otherwise legitimate instances.
• Within the term. Establish that the deployment existed during the term, which the evidence file supports with dates.
• Metric and core factor. Apply the correct processor core factor or Named User Plus rule, so each in scope deployment is counted accurately.
• Evidence. Attach the records that prove each figure, so the reconciled count is defensible at certification and in any later audit.

A reconciliation in miniature, indicative

The table below shows how reconciliation reshapes a raw measurement into a defensible count for an anonymized example. The figures are indicative and exist to show the logic, not to represent any real engagement.

Indicative only. The direction and size of each adjustment depend entirely on the estate and the wording of the specific agreement. The point is that the reconciled number differs from the raw one in both directions.

The out of scope instances are a finding, not a loss

One of reconciliation's most valuable outputs is the list of deployments that do not count, because identifying them early turns a future problem into a managed decision. An out of scope instance discovered in reconciliation can often be brought into scope through an amendment, relocated so that it counts, or licensed deliberately, all while you still have time and leverage. The same instance discovered by Oracle in a post certification audit is a remediation demand. Reconciliation is where you find these instances first, on your own terms, which is exactly where you want to find them.

This is why reconciliation belongs at the heart of any certification, not as a final tidy up but as the exercise that produces the number itself. It is also why it should be done before the window, when the levers to act on what it surfaces are still open. A reconciled count is the deliverable a certification letter should be built on, because it is the only version of the number that has been tested against the contract and backed by evidence, and therefore the only version anyone should be asked to sign.

The next step

Reconciliation is the discipline that turns a measurement into a certified count you can defend, and it is the natural moment to resolve scope and evidence together. If your window is near, an independent reconciliation is the fastest way to a number you can sign. See how to establish the raw figure in verifying the count before Oracle does, capture a commonly missed source in does disaster recovery count at certification, and ground the whole approach in our Oracle ULA certification guide.