Exiting an IBM ULA without a surprise bill.

An IBM Unlimited License Agreement ends with a certification, and that certification sets your perpetual entitlements for everything you deployed during the term. Done well, you walk away owning a large, fixed estate. Done carelessly, the exit becomes the next audit, with a true up bill attached.

What the ULA certification really does

A ULA lets you deploy a defined set of IBM products without counting during the term, in exchange for a fixed commitment. The catch sits at the end. To exit, you certify your deployment as of the close date, and that certified number becomes your perpetual entitlement going forward. There is no second chance to recount. Whatever you can defensibly demonstrate on the certification date is what you own, and whatever you cannot is either dropped or treated as a shortfall.

This is why a ULA exit is structurally an audit in everything but name. IBM has a direct interest in how the count is drawn, because a higher certified number means more support revenue, while a contested or understated number opens the door to a compliance claim. The buyer interest is the mirror image: certify the full, legitimate deployment so the perpetual grant is as large as the term genuinely earned, without overstating in a way that inflates future support.

Where the surprise bill comes from

• Deployment that grew during the term but was never measured, so the certification understates what you are entitled to keep.
• Products used outside the ULA scope, which do not convert and instead surface as unlicensed use at exit.
• Sub capacity positions that were never backed by continuous ILMT data, collapsing to full capacity counts at the worst moment.
• A certification accepted on IBM numbers rather than your own, with no independent baseline to challenge it.

The pattern is consistent. The bill is rarely a surprise in the deployment itself. It is a surprise because the buyer arrived at the certification date without an independent measurement and had to react to IBM figures under a deadline, instead of presenting a defensible count built in advance.

How to exit on your own numbers

Measure the estate before you certify

The single move that prevents a surprise is an independent deployment baseline taken well before the close date, the same measurement discipline used in a defense. That means a full estate inventory documented before anyone asks for it, with PVU and sub capacity positions reconciled against entitlements. When you hold your own number first, the certification becomes a confirmation rather than a negotiation you are losing.

Validate the sub capacity claim early

Sub capacity rights are the most fragile part of any ULA exit, because they depend on ILMT having run continuously with quarterly reports retained. If the agent coverage lapsed during the term, those periods default to full capacity counting, and the certification inflates accordingly. Confirming the sub capacity record is intact before certifying is what keeps the perpetual grant honest and the support base from ballooning.

Treat the certification as a negotiation

The certified figure is not a clerical formality, it is a negotiated position, and it carries the same dynamics as an ELA true up. Overstated deployment, denied sub capacity, and scope disputes are all contestable when you bring evidence, and that is where exit findings move within the 30 to 92% reduction range our engagements deliver.