How to Defend Against a Java True Up at Renewal

An Oracle Java true up recaptures headcount growth every anniversary and feeds it straight into the bill, rarely adjusting down when your population falls. Reset the base first, then remove or cap the clause.

The true up is the renewal trap that compounds

Of all the terms in an Oracle Java agreement, the annual true up does the quietest and most lasting damage. Since January 2023 the Universal Subscription is priced per employee, and a true up recaptures any headcount growth at each anniversary and feeds it straight into the bill. A growing company therefore pays more for Java every year, regardless of whether its Java use changed at all. At renewal the accumulated true ups become the new baseline. Defending against the true up is one of the highest value moves in any renewal. For where it sits in the overall plan, see the Java renewal strategy guide.

How a true up actually works

A true up clause obliges you to remeasure your counted population at each anniversary and pay for any increase. Because the metric counts every full time and part time employee, every contractor, and every temporary worker, the population tends to drift upward through hiring, contractor use, and seasonal staffing. The true up captures all of it. Critically, most true up clauses are one directional: they catch growth but do not reduce the bill if the population falls. That asymmetry is the heart of the problem and the focus of the defense.

The defenses, in order of value

There are several ways to defend against a true up, and they stack.

• Remove it: negotiate the true up out entirely, fixing the counted population for the term so growth does not lift the bill.
• Make it two directional: if it stays, insist it adjusts down as well as up, so a shrinking population lowers the bill.
• Cap it: limit the annual increase to a stated percentage, so a hiring surge cannot trigger an open ended jump.
• Shrink the base first: reset the population and migrate replaceable workloads before the true up measures, so it captures a smaller number.
• Fix the measurement date: pin a representative date rather than a seasonal peak, so timing does not inflate the increase.

Removing the true up is best. Where Oracle resists, a capped, two directional true up on a reset base is a strong fallback.

A worked defense

The figures below are indicative. They show the difference the defense makes over a three year term.

Year	Open true up	Defended
Year 1 baseline	$792K	$640K
Year 2 after growth	$881K	$640K
Year 3 after growth	$975K	$640K

The figures are indicative. The open true up column climbs every year as headcount grows. The defended column holds, because the population was reset and migrated down first and the true up was capped or removed. Over the term the gap is substantial.

Reset the base before you negotiate the clause

The true up multiplies whatever base it measures, so the most powerful defense starts before the clause itself. Reset the counted population with documented evidence and migrate replaceable workloads to a free OpenJDK distribution, so the number the true up will measure is already smaller. A capped true up on a reset base is far better than a removed true up on an inflated one. Sequence the population reset first, then negotiate the clause. For the reset method, read start your Java renewal twelve months out.

Watch how the true up interacts with the floor

The true up rarely travels alone. Read it alongside the minimum annual floor, because together they form a one way ratchet. The true up lifts the bill when your population grows, while the floor stops it falling when your population shrinks. A company that hires through a good year and then contracts in a lean one can find that the true up captured the growth but the floor blocked the relief, so the bill only ever moved upward. Defend the two terms as a pair. A capped, two directional true up loses much of its value if a high floor sits underneath it, so negotiate the floor down in the same conversation and make sure the agreement can actually reward a smaller workforce, not just punish a larger one.

Get the measurement mechanics in writing

Much of the damage a true up does comes from vague mechanics. The clause should state precisely when the measurement is taken, which populations it includes, what source of record governs, and how disputes are resolved. Left undefined, the measurement defaults to whatever reading Oracle prefers, which is the largest one available. Pin the mechanics in the contract: a named measurement date, the systems of record that govern the count, and a right to reconcile before any increase is billed. Clear mechanics convert the true up from an open ended exposure into a defined, predictable item you can plan around. For the documentation that backs the measurement, see documenting headcount for a Java negotiation.

Hold the line under the 2026 audit

LMS audits intensified in 2026 with a three year lookback centered on employee count and contractor inclusion, and the true up is exactly where audit findings turn into recurring cost. Oracle will push for the largest population at the anniversary measurement. Answer with dated, reconciled evidence, share only what the contract obliges, and never accept a true up figure under deadline pressure. A documented population is the only thing that holds a true up honest. For the broader strategy that ties it together, see the Oracle Java renewal strategy guide.

The buyer side takeaway

The annual true up is the renewal trap that compounds, capturing headcount growth every year while rarely reducing the bill when the population falls. Defend it by removing it, or by making it two directional and capped on a reset, migrated base, and always fix a representative measurement date. Sequence the population reset before the clause negotiation, because the true up multiplies whatever base it finds. Download the Java Renewal Defense Checklist below to run the defense.