Licence True-Ups: The Invoice for Users You Added Months Ago

Most software is sold per user. Twenty seats, a negotiated rate, an annual invoice. Simple enough, and easy to budget for.

Then the business does what businesses do. A new starter joins in February. A contractor needs access for a project. Two people move into a team that uses the tool. Somebody in IT, reasonably, adds them.

Nobody raises a purchase order, because nobody thinks of it as a purchase. It is a login.

Eleven months later an invoice arrives for all of it — often at a higher rate than you negotiated, and backdated to the day each person first signed in. This is a licence true-up, and it is one of the most reliable surprises in software contracting.

How a true-up works

Your contract licenses a number of users, usually with a discount against the supplier's list price. It also contains a provision for what happens when you exceed that number.

The common structures:

Annual reconciliation. The supplier counts actual users at a fixed point each year, compares it with what you paid for, and invoices the difference.

Retroactive billing. The additional users are charged from the date they were first provisioned, not from the date of the invoice.

List price for additions. Your negotiated discount applies to the committed base only. Anything above it is billed at the supplier's standard rate.

Automatic provisioning. The system lets administrators add users freely, with no warning that doing so creates a charge.

Each of these is defensible on its own. Together they produce a bill that nobody approved, for usage nobody tracked, at a price nobody negotiated.

What it costs

Take a twenty-seat contract at a negotiated £30 per user per month, against a list price of £45.

In April you add six users. The true-up is calculated the following March, eleven months later.

	At your negotiated rate	At list price (as contracted)
Six users × eleven months	£1,980	£2,970

That £990 difference is the discount you thought you had and did not. And it is not the whole cost. At renewal the supplier will usually propose resetting your base to twenty-six seats — at whatever rate they can achieve — so the additions do not merely generate one invoice, they permanently raise your floor.

The seats nobody gives back

True-ups count upwards. They rarely count downwards.

People leave. Projects end. Contractors roll off. Their accounts are deactivated, or more often simply forgotten, and in most per-seat agreements you cannot reduce your licence count during the term regardless. The seat you paid for in January remains paid for until renewal, whether or not anyone uses it.

So a business can simultaneously be paying for five idle licences and receiving a true-up invoice for six new ones. The two never net off, because they are governed by different clauses. This is the same asymmetry that makes minimum spend commitments expensive: obligations that ratchet up easily and come down only through negotiation.

Why it goes unnoticed

It is not a purchase. Adding a user feels like administration, not spending. It happens in an admin console, not through procurement.

The person adding users is not the person who signed the contract. Usually IT, or a team lead with admin rights, neither of whom has read the pricing schedule.

The invoice arrives long after the decision. By the time the true-up lands, the additions are months old and entirely normal. Disputing them feels like disputing reality.

Your budget was set on the committed number. Nothing in the finance system knows the real user count is climbing.

What to negotiate at signature

Additional users at your discounted rate. The single most valuable change. If the business grows, you should not be penalised with list price for doing so. Suppliers concede this more often than buyers expect, because growing accounts are exactly what they want.

True-ups billed from the reconciliation date forward, not retroactively. You pay for extra users from when the count is agreed, not from when someone first logged in.

A flex-down right at renewal. The ability to reduce seats to actual usage, without penalty, at each renewal. Pair it with the right to reduce during the term if headcount falls materially.

A buffer. A small allowance — say 10% above the committed number — before any true-up applies. It absorbs normal fluctuation and removes the administrative friction of chasing single seats.

Notice before overage. A requirement that the supplier tells you when you exceed your licensed number, rather than letting the count grow silently until reconciliation.

The leverage for all of this exists at signature and, to a lesser extent, before your notice deadline. As covered in our conversation about how supplier sales teams work, a low first-year price can hide licence escalation — and true-up terms are where that escalation lives.

What to do this quarter

Find your per-seat contracts. Anything priced per user, per seat, per licence or per named account.

Compare licensed against actual. Most admin consoles show active user counts. You are looking for two numbers: users above your licence (a true-up coming) and inactive accounts below it (money you are already wasting).

Deactivate the idle accounts — but check whether that actually reduces your charge. Often it does not until renewal, which is exactly why the renewal is where the conversation should happen.

Find the reconciliation date. It is frequently not the renewal date, and it is the date that determines when the invoice arrives.

Decide who can add users. Not to stop it — the business needs the access — but so that someone who knows the pricing is aware when it happens.

What to record

For each per-seat contract:

• The licensed user count and the per-user rate
• Whether additional users are billed at your rate or list price
• Whether true-ups are retroactive or forward-only
• The reconciliation date, separately from the renewal date
• Whether you can reduce seats, and when

That last pair of dates matters most. The reconciliation tells you when the bill arrives; the renewal tells you when you can change the terms that produced it.

And the renewal is the one to protect. A true-up invoice is largely already decided by the time it lands — the users were added, the clause says what it says. The terms that produced it can only be renegotiated at renewal, which is precisely the date most likely to pass unnoticed. Timemy tracks renewal and notice dates and reminds you at 90, 30 and 7 days, so that conversation happens while you still have leverage. See how contract tracking works.

---

The short version: per-seat software contracts often bill additional users at list price, backdated to when they first signed in, at an annual reconciliation nobody has diarised. Ask at signature for additions at your negotiated rate, forward-only true-ups, a flex-down right at renewal and a small buffer. And count your idle licences — you are probably paying for seats nobody uses while being invoiced for ones they do.