Budget Season is upon us: Plan, Predict, Control

Mainframe software is one of the largest and least visible lines in most IT budgets. It’s rarely a single product — it’s an estate of licenses, tiers and capacity-based agreements built up over years, priced against things that move, and understood in detail by only a handful of people in the organization.

Which is why every autumn the same three things land at once:

1 – The annual price adjustment arrives, effective January 1st.

2 – The 2026 true-up needs settling.

3 – And someone in finance wants a defensible number for 2027.

Here’s what’s actually going on, and what to do about it before the year closes.

Three things worth knowing

January 1st is about predictability, not opportunism. Vendors align adjustments to a single date so the price you’re told in the autumn holds for the whole calendar year. And the adjustment itself is less mysterious than it sounds: the costs behind the software — developers, support, hosting, third-party components, compliance — go up every year. Small predictable steps are the less painful version of a large correction later.

A true-up is a meter reading, not an audit. Mainframe software is priced against something that moves — capacity, MSUs, cores, processed volume. You agree to a baseline at the start of the year and compare it against what you actually consumed at the end.

The important detail is that this usually only moves one way. In most agreements the baseline is fixed: you’ve committed to it, and if you consumed less than you committed to, that isn’t refunded – unused volume is typically carried forward to the following year’s baseline instead and lost altogether when the contract expires. What affects your budget is the overspend — underspend is neglected. There’s a second consequence worth planning for. If the true-up shows you’ve grown past what your agreement covers, settling last year’s overspend is only half of it — you may also need additional licenses or a higher capacity tier going forward. That’s a permanent step up in the run rate, not a one-off invoice, and it belongs in the 2027 budget rather than arriving as a surprise in February.

Surprises are almost always your own growth. A large true-up is rarely caused by the vendor. It comes from migration, acquisition or new workload within your organization that never reached the budget owner. That’s fixable — but only if IT and finance talk before end of year.

Where it usually goes wrong

Notice what all three points have in common: they depend on knowing your own numbers.
Most organizations don’t, at least not precisely. Consumption data sits in technical systems that finance can’t read, in a format that answers “how is the system performing?” rather than “which part of the business used this, and what did it cost?”

So, the true-up becomes a disclosure instead of a discussion. Growth gets described as “usage went up” because nobody can say whose usage went up. And the 2027 budget line becomes last year’s figure plus a round number nobody can defend.

How ITBI changes that conversation

This is the gap ITBI is built to close, and the heart of it is business mapping: connecting technical consumption to the business areas, services and applications that caused it.

That single translation is what makes the rest possible.

Growth gets a name and an owner. Instead of “consumption rose 12%” you can say which business area grew, by how much, and since when. Example: “the claims system grew 10% after the Q2 migration”, or “the reporting suite quietly doubled after the new account statements”. A number with a cause is a number you can plan around. A number without one is just a bill.

Optimization opportunities become visible. Once consumption is mapped to business areas, the outliers stand out on their own: workloads that grew without anyone asking for it, jobs running far more often than the business actually needs, peaks that push you into a higher licensing tier, capacity still attached to services that were decommissioned months ago. Anomaly detection surfaces the spikes worth an hour of investigation. Customers typically find 15–20% of capacity-related cost is addressable once someone can finally see it.

You see the overspend coming. ITBI tracks actual consumption continuously against your baseline, so drift above it shows up in month three rather than at the year-end reconciliation. Since the true-up only really moves in one direction, that lead time is the difference between managing the overspend and paying for it.

The 2027 line becomes defensible. Take actual 2026 consumption as the base, apply the contractual adjustment, add the known changes per business area, and forecast the trend. Three visible components instead of one opaque figure carried forward — and if the trend says you’ll cross a license threshold in the second half of 2027, you can budget for it now instead of discovering it at the next true-up.

Cost gets an owner. Cost allocation and chargeback put consumption next to the business unit that drove it. Costs that belong to someone tend to get managed. Costs sitting in a central IT bucket rarely do.

The short version

An annual increase isn’t a renegotiation. A true-up isn’t a penalty — but it is usually one-directional, so the only real protection is seeing the overspend coming. And the unpleasant surprises came from usage nobody was tracking back to a business owner.
So, the real question isn’t whether the price goes up on January 1st. It’s whether you can point at a business area and say: this is what you consumed, this is why it grew, and this is what we can stop paying for.

That’s a visibility problem before it’s a pricing problem.

Realistically, it’s probably too late to change this year’s numbers. The 2026 consumption has already happened, and the true-up will say what it says. But it isn’t too late to make sure next year is different — so that in twelve months you’re reading your own figures rather than reacting to someone else’s.

If you want to learn more about how our ITBI platform and our team of Mainframe Experts can help solve these issues for your organization please reach out to our CCO, Jan Vilstrup (jvi@smtdata.com) and book an informal 20 minute meeting.