How ALA bundles obscure true entitlement

Software is often sold as a bundle: a suite of components, a set of modules, or a product packaged with the tools around it, all granted under a single authorization at a single price. That convenience at purchase becomes a liability at audit. How ALA bundles obscure true entitlement is the question of what a bundled grant actually licenses, because a finding that pulls a bundle apart and prices each component as if it were bought separately can manufacture a shortfall out of a grant the buyer fully holds. The bundle is one entitlement; a finding that unbundles it counts several.

This field note explains how bundled authorizations work, where a finding inflates by separating what was sold together, and how the defensible reading holds the count to the bundle as it was actually purchased. It pairs with our ALA and entitlement review track.

What a bundled authorization grants

A bundle grants a defined set of components under common terms. The components may include several products, modules of one product, or a product together with adjacent capabilities, and the grant covers them as a package. The metric may apply to the bundle as a whole, or to a primary component with the rest included, and the price reflects the package rather than the sum of its parts sold individually. Reading the bundle correctly means understanding what it included, how the metric applied across it, and what use of the components the single grant permitted. The bundle is a unit, and its entitlement is the unit, not a collection of separable line items.

How a finding unbundles the grant

The inflation mechanism is separation. An auditor takes a component that was included in the bundle, treats it as a standalone product, and prices it at the standalone list price as though it had never been licensed. Or the auditor applies the bundle's metric to one component while ignoring that the same metric already covered the others, counting the same usage more than once. Or a module that the bundle included is treated as an unlicensed add on. Each of these reads the package as if it were separable, and each adds to the finding a charge for something the single grant already covered. This is a close relative of the metric substitution we describe in ALA metric definitions versus the order form, applied to the structure of the grant rather than its unit.

Why bundles are hard to reconstruct

Bundles obscure entitlement precisely because the components are not always listed the way they are deployed. A bundle bought years ago under one product name may now run as several differently named modules, and the connection between what was purchased and what is deployed is not obvious from the deployment alone. Reconstructing that connection, mapping each deployed component back to the bundle that licensed it, is the work that defeats an unbundling finding. It is the same reconstruction discipline we apply to layered grants in stacked and superseded ALAs in a license estate, and it depends on the entitlement baseline set out in how to build an ALA entitlement baseline.

The order form anchors the bundle

The strongest evidence that components were bought together is the order form that bought them. A single line covering a named bundle, at a single price, establishes that the components inside it are one grant rather than several. A finding that prices a component separately can be answered with the order line that shows it was included in the package the buyer purchased. The order form is where the bundle's unity is recorded, and producing it ends the argument that the component was unlicensed, a point we develop in reducing an ALA finding with order form evidence.

How we defend the bundle as bought

Our defense reconstructs each bundle from the authorization and the order form that granted it, then maps the deployed components back to the package that licensed them. We establish what the bundle included, how the metric applied across it, and which deployed modules the single grant covered, then show where the finding separated the package and priced its parts as standalone products. Where the finding has unbundled a grant the buyer fully holds, the duplicated and standalone charges are removed and the count is held to the bundle as purchased. This is the Reconstruct and Rebut work of our method, and recovering entitlement that a finding had double counted is the kind of correction that moved our E-02 case file, a developer seat overclaim, from $4.5M to $0.9M, an 80 percent reduction, once the grant was read as it was actually bought.

One price is a signal of one grant

When the documents are ambiguous about whether components were sold together or separately, the price is often the clearest signal. A single price for a named package, set below the sum of the components priced individually, is strong evidence that the buyer purchased one grant rather than several, because the discount only makes sense if the package was the unit of sale. A finding that prices each component at standalone list ignores not only the structure of the grant but the economics of the purchase, charging the buyer as though it had paid for separate products when it paid for a package. Reading the price alongside the order line and the authorization restores the bundle as the unit the buyer actually bought, and it exposes the standalone pricing as a reconstruction the original transaction does not support.

Closing the bundle question forward

Once the present finding has been corrected, the forward agreement should record the bundle plainly: what it includes, how the metric applies across the components, and that the package is one grant rather than separable line items. A clean forward arrangement removes the ambiguity that let the audit pull the bundle apart, so a future review starts from an agreed package rather than a contested set of components. Resolving the finding and recording the bundle forward are two halves of the same work. If a finding has separated a bundle you bought as one grant, open a case and we will hold the count to the package you actually purchased.

For the full method, read the complete OpenText audit defense playbook, and for entitlement defense across the Micro Focus estate see our ALA and entitlement review track.