Annual True Up Triggers in Java Contracts

Here is the short answer. An annual true up is the clause that resets your Oracle Java subscription to your current employee count each year, and it almost always moves the bill up. As you hire, acquire, or add contractors, the count rises and the charge follows. It rarely moves down, because a minimum annual floor usually catches it. The triggers are anything that grows your counted population. You manage the true up by capping the increase, narrowing the definition, and tracking the count yourself before Oracle does.

The true up rides on the per employee Universal Subscription that Oracle introduced in January 2023. Pricing runs from 5.25 to 15.00 dollars per employee per month, and the metric counts every full time and part time employee, every contractor, and every temporary worker, regardless of who uses Java. Because the basis is your whole workforce, anything that grows the workforce grows the bill. The complete renewal method is in our Java renewal strategy guide.

What actually triggers a true up

The trigger is a change in your counted employee population between measurement points. Several ordinary events set it off. Organic hiring across the year raises the number. An acquisition folds a new workforce into your count. A seasonal expansion that brings in temporary workers counts them in full. A growth in contractors, even on short engagements, adds to the basis. None of these has anything to do with how much Java you actually run, yet each one can raise your Java bill.

That disconnect is the core unfairness. You can hold your Oracle Java usage flat, or even reduce it, and still face a higher charge simply because the business grew. The true up measures people, not software.

Why the true up rarely works in your favor

In theory a true up could adjust in both directions. In practice it is paired with a minimum annual floor that prevents the bill from falling, a mechanism we explain in the minimum annual floor in Java agreements. The two clauses work as a ratchet. The true up lifts the bill when you grow, and the floor holds it when you shrink. The result is a charge that only knows how to climb.

With Oracle audits intensified in 2026 and a three year lookback in play, Oracle also has more occasions to revisit your count and apply the true up against a fuller history. That makes it all the more important to control the definition and keep your own records.

How to manage the true up

Begin with a cap. Negotiate a firm limit on how much the subscription can rise at any true up, so a year of growth or an acquisition cannot produce an uncapped jump. A cap turns an open ended risk into a known maximum you can budget for.

Next, narrow the definition. The broader the employee definition, the more events trigger an increase. Push for the tightest reasonable basis, exclude populations that should not count, and define exactly when and how the measurement is taken. The definition does as much work here as the rate.

Then, measure yourself first. Track your counted population on your own terms throughout the year, so you arrive at each true up with a number you can defend rather than accepting Oracle's. The true up is part of a connected set of clauses, and the full list to address together is in the Java contract traps to negotiate out.

Turn the true up into a known quantity

A well negotiated true up is predictable. You know the cap, you know the definition, and you measure the count yourself. That control is part of how our clients have cut an average of 68 percent off Oracle's opening number, with more than $120M in Java exposure defended across more than 300 audits and more than 20 years of combined experience.

If your current agreement has an uncapped true up, or if a renewal is approaching and you are unsure what the next adjustment will bring, it is worth talking it through before the number lands. A short conversation can show you where the exposure sits and what can still be capped or redefined while you have leverage.