Proof of Entitlement documents and why they matter.

The Proof of Entitlement, or PoE, is the document that records what you are licensed to run, in what quantity, under which metric. In an audit it is the single most important piece of paper you own, because the deployment is measured against the entitlement the PoE proves, not the entitlement you remember buying.

What a Proof of Entitlement records

A PoE is IBM issued evidence of an entitlement granted under Passport Advantage. It names the program, the version where relevant, the metric the program is licensed under, and the quantity granted. It ties that entitlement to a Passport Advantage site and the legal entity that holds it. Together with invoices and the agreement itself, the PoE is what establishes the legitimate ceiling for your deployment of a given product.

The reason it carries so much weight in an audit is simple. An auditor measures what is installed and running, then compares it to what you can prove you are entitled to. Anything you cannot evidence does not count toward your position. A deployment that is genuinely covered can still read as a shortfall if the matching PoE cannot be produced.

Where the PoE trail breaks down

• Entitlements bought years ago through a reseller, with no PoE retained internally.
• Acquired entitlements where the PoE stayed with the prior owner and never transferred.
• Trade ups and version changes that supersede an older PoE, leaving an unclear chain.
• Bundled entitlements where the PoE describes a suite, not the component actually deployed.

The common thread is that the entitlement is real but unprovable at the moment it matters. By the time an audit asks, reconstructing a PoE trail from invoices, reseller records, and Passport Advantage history is slow work, and the clock is rarely on your side.

How we use the PoE in a defense

Assemble the entitlement record first

Before any deployment count is conceded, we build the documented entitlement position from the PoEs, invoices, and agreement together. That record is the baseline every finding is tested against. Reconciling deployment to a complete PoE trail is the foundation of an audit defense, and it routinely converts an apparent shortfall back into a covered position.

Close gaps before they become findings

Where a PoE is missing, we work the supporting evidence to reconstruct the entitlement and document the chain, so the auditor is met with proof rather than a blank. A clean, current PoE library is also what makes a future contract harmonisation or transfer defensible rather than disruptive.