The software licence audit letter: what to do in the first week

Photo: rawpixel via rawpixel (CC0 1.0)
The letter is polite. It thanks you for being a valued customer, refers to a clause in an agreement signed by someone who left in 2017, and asks you to confirm a date for a review of your deployment. It’s an audit. The vendor already has a number in mind, that number is the reason you were selected, and what you do in the first seven days will shape whether you pay it. I’ve been through four of these from the customer side, at the freight company and at the hosting business, and one from the other side, briefly, as a contractor. Here’s the week.
Day one: read the contract, not the letter #
The audit right is in your agreement, and its terms matter more than anything in the letter. How much notice must they give? Who conducts it, the vendor or a third party? What are you obliged to provide: access, data, or “reasonable cooperation”? How often can they audit? Is there a confidentiality clause covering what they find? Pull the master agreement, every order form and every amendment, because the rights and the licence metrics often changed between them. If you can’t find the contract, that’s your first finding and it isn’t a good one.
Then tell three people: legal, procurement and whoever signs the cheques. Not the whole IT department, not yet. An audit that becomes office gossip becomes an audit where helpful people start uninstalling things, which vendors treat as evidence rather than good housekeeping.

Day two: reply, briefly, and set the terms #
Acknowledge the letter in writing. Confirm you’ll comply with the contractual audit provisions, and propose a timeline that gives you the notice period you’re entitled to, in full. Ask which products and which metrics are in scope, in writing, and don’t accept “all products”. Ask who’s conducting it and whether they’re paid on findings, because some third-party auditors are, and you’re entitled to know. Propose that all data be exchanged under the confidentiality terms of the agreement and that nothing leaves your control without your review. Vendors expect this. A customer who replies “sure, come Tuesday” is telling them something.
Days three to five: count it yourself, first #
This is the whole game. Before the vendor’s tool touches your network, you need your own count of what’s installed, what’s actually used, and what you’re entitled to. The result is called an effective licence position, and it’s a spreadsheet with three columns: deployed, used, entitled. The difference between the first and the third is the exposure; the difference between the first and the second is your negotiating room.
Use your own discovery tooling if you have it and a contractor who does this for a living if you don’t. Count everything the vendor might count: production, test, disaster recovery, the virtual machines that were cloned for a project and never deleted, the developer laptops, the instance somebody spun up in a cloud account with a corporate card. The auditors will find all of it. Finding it first means you can uninstall what’s genuinely unused before the scan, which is legitimate, and understand what’s genuinely needed, which is where the negotiation goes.
Pay particular attention to the metrics. Vendor licensing is measured in processors, cores, named users, concurrent users, employees, revenue, “indirect access” and combinations that seem designed to be misread. A database licensed per core on a virtualised host may, under some vendors’ rules, be counted on every core in the cluster, not just the ones the virtual machine uses. That single interpretation has been the basis of eight-figure findings.
The Java clause that caught everyone #
The example I use to explain why this matters is Oracle’s change to Java licensing in January 2023. The company moved its Java SE subscription from a per-user or per-processor model to a per-employee model: every employee in the organisation, whether or not they’d ever seen a line of Java, counted toward the price. Organisations that had a couple of hundred developers using Java found themselves quoted for their entire headcount. Many of them had never consciously licensed Java at all, because for years it had been free to use, and the audit letters that followed were, for a lot of Australian mid-sized companies, the first they’d heard of it.
The lesson isn’t about Oracle specifically. It’s that the metric can change under you between agreements, and the audit measures against the current one. If you haven’t read your current terms, you don’t know what you’re being counted on.
Days six and seven: prepare the room #
Decide, before anyone arrives, what the auditors get. Usually that’s the output of an agreed discovery script, reviewed by you first, not live access to your systems and not a raw export of everything. Nominate one person to handle every request and log every exchange. Brief the technical staff who’ll be in the room that they answer the question asked, factually, and don’t volunteer history, opinions or the phrase “we’ve probably got more of those somewhere”.
And set the objective. It’s rarely “pay nothing”. It’s usually “pay for what we need, on terms we’d have accepted anyway, without back-maintenance and penalties”. Vendors run audits to sell, and the finding is the opening position for a sale. A customer who arrives at the table with an accurate count, a clear view of what it actually needs for the next three years and a willingness to buy that, tends to end up with a commercial deal rather than a compliance bill. The ones who arrive with nothing get the list price.
The four findings that come up every time #
After enough of these you can predict the report before it’s written, because the same four things account for most of the money.
Virtualisation. A product licensed per processor or core, running on a virtualised host, counted by the vendor against the whole physical cluster rather than the allocated virtual resources. Different vendors have different rules for which virtualisation platforms they’ll recognise as “hard partitioning” and which they won’t, and the difference can be a factor of ten. Know the rule before the scan. If your platform isn’t on the vendor’s approved list, the cluster is the count.
Disaster recovery. The standby copy of the database, switched off, waiting for the day the primary fails. Some agreements license it free if it’s cold, some charge for warm standby, some charge for anything installed. The people who set it up assumed it was free because it wasn’t running. The auditor doesn’t share that assumption.
Indirect access. A third-party application that reads from or writes to the vendor’s system through an interface, on behalf of users who never log into the vendor’s product. Several large vendors take the position that those users need a licence anyway. This is the finding that produces the truly startling numbers, and it’s the one where the contract wording matters most, because agreements written before the vendor adopted the position often don’t support it.
Leavers. Named-user licences assigned to people who left three years ago, never deprovisioned, still counted. This one’s pure housekeeping and it’s the easiest money to save before the scan, since it’s the one place where uninstalling and deactivating is unambiguously legitimate: the person doesn’t exist.
Handle those four and the audit becomes, mostly, a conversation about what you’d like to buy next. Handle none of them and you’ll be reading a finding that begins with a number and ends with a proposal for a new enterprise agreement, which was the point all along.
A note on tone, since it comes up. The auditor in the room is doing a job and is usually a perfectly reasonable person; the pressure is coming from a sales target three levels above them. Be courteous, be precise, be slow. Every request gets a written answer within the agreed timeframe and not before. You are not being obstructive by taking the time the contract gives you, and an auditor who suggests otherwise has told you which of you understands the agreement.
The longer fix #
None of this is avoidable, but most of the drama is. A software asset management practice, which is a grand name for someone who keeps the entitlements register current and reconciles it against discovery twice a year, turns the audit letter from a crisis into a calendar entry. The Digital Transformation Agency negotiates whole-of-government agreements with the major vendors precisely because individual agencies kept losing this fight on their own, and the private sector’s equivalent is simply reading the contract before the vendor does. The ACCC has taken an interest in unfair contract terms in business-to-business software agreements in recent years, and if a clause in yours looks like it was written to be tripped over, it’s worth raising with legal before you sign, not after the letter arrives.
The opinion I’ll offer is this: the industry treats audits as adversarial because they usually are, and the vendors would sell more, over time, if they weren’t. But that’s their problem. Yours is the count. Do the count.
— Anjali Mehta, Enterprise & Cloud Editor, Technology Spectator