Software you deploy quietly drifts away from software you have paid for. A tag added here, a client installed there, a system copied to a spare - over years, a SCADA deployment can end up using more than its entitlements allow without anyone noticing. A license audit is when the vendor asks you to prove otherwise, and a true-up is the bill that follows if you cannot. This guide explains what happens in a software audit of a SCADA deployment, how installed tags and seats are reconciled against what you own, what a true-up costs, and how tracking deployed-versus-licensed keeps audits from turning into surprise penalties.
License audit and true-up in one line: A license audit is a review, often initiated by the software vendor, that reconciles what a customer has actually deployed - tags, client seats, servers, and features in use - against the entitlements they have purchased. A true-up is the transaction that closes any gap the audit finds, meaning the customer buys additional licenses to cover the over-deployment. Teams avoid unpleasant audit outcomes by continuously tracking deployed versus licensed rather than discovering the gap when the vendor asks.
A software audit is a structured comparison between deployment and entitlement. The vendor, or an auditor acting for them, seeks to establish what the customer is actually running - how many tags are configured, how many client seats are in use, how many servers the software is installed on, and which licensed features are enabled - and then compares that reality against the licenses on record. The audit may draw on usage reports the software itself produces, on records the customer supplies, and on inspection of the deployed systems, with the aim of arriving at an agreed picture of what is deployed versus what is owned.
The reconciliation is only as clean as the customer's own understanding of their estate. If a team knows precisely how many tags and seats each system uses and can map every deployment to a license, the audit is a confirmation exercise. If instead the deployment has grown organically and nobody has kept a current tally, the audit becomes a scramble to reconstruct what is actually running, often surfacing installations and expansions that were never tracked against entitlement. The gap between what people think is deployed and what is truly deployed is where audit surprises live.
Audits are a normal feature of the commercial relationship in software licensed by tags, seats, or features, not an accusation. Vendors have a legitimate interest in confirming that usage matches what was paid for, and many license agreements explicitly reserve the right to audit. Approaching an audit with organised, current records turns it from an adversarial event into a routine reconciliation, whereas approaching it unprepared invites both the effort of reconstruction and the risk of discovering an expensive gap.
When an audit finds that deployment exceeds entitlement, the resolution is a true-up: the customer buys the additional licenses needed to bring their entitlement up to their actual usage. In principle this is simply paying for what you are using, and the true-up closes the gap so the deployment becomes compliant. The complication is that a true-up discovered by audit is negotiated from a weak position - the over-deployment already exists, so the customer is buying under pressure rather than planning a purchase on their own terms, which is a poorer place to negotiate from than a proactive expansion.
The cost of over-deployment can exceed the plain price of the extra licenses. Because the gap represents usage that was not paid for at the time, remedies can include not just the list price of the shortfall but additional charges, lost negotiating leverage, and the internal cost of the reconciliation effort itself. The details depend entirely on the specific agreement, and this page does not assert any particular penalty, but the general principle holds: closing a gap under audit is typically less favourable than having stayed compliant or having expanded deliberately, which is why over-deployment is a risk to manage rather than a routine cost.
There is also an operational dimension to over-deployment beyond the money. A deployment that has quietly grown past its tag or seat limits may be relying on grace behaviour or on the vendor not yet having noticed, which is not a stable footing for a control system that has to keep running. Bringing entitlement into line through a true-up removes that latent exposure, so the value of resolving it is not only avoiding penalty but restoring the certainty that the software is fully and legitimately licensed to keep doing its job.
The defence against audit surprises is continuous tracking rather than periodic panic. Keeping a live record of how many tags and seats each system uses, and mapping every deployment to the license that covers it, means the answer to any audit is already known. Many SCADA products expose usage information - current tag counts, active sessions, enabled features - that can be gathered into a running picture, and pairing that with an entitlement register turns compliance from an occasional reconstruction into a standing dashboard. The discipline is unglamorous but it is what converts an audit from a threat into a formality.
Tracking matters more in SCADA than in ordinary office software because SCADA deployments grow in ways that are easy to miss. Tags accumulate as new instruments and calculations are added, systems get cloned for test or spare, and expansions happen at remote sites out of sight of whoever holds the licenses. Each individual change is small and reasonable, but collectively they drift the deployment away from entitlement, and without an owner watching the total, the drift is invisible until an audit makes it visible all at once. Assigning clear ownership of the deployed-versus-licensed figure prevents that slow, unwatched creep.
Cloud SCADA changes the tracking problem by centralising both the deployment and its measurement. On a platform such as Merobix, the tags and access for a fleet of remote sites live in one managed system, so the count of what is deployed is inherently visible rather than scattered across sites that each have to be inventoried. For a distributed oil and gas operation, that means the deployed-versus-licensed picture is maintained continuously in one place as part of running the platform, which removes much of the reconstruction effort an audit would otherwise demand and keeps entitlement aligned with usage as the estate grows.
An audit is the review that reconciles what you have actually deployed - tags, seats, servers, and features in use - against the licenses you own. A true-up is the transaction that follows if the audit finds you are using more than you paid for: you buy the additional licenses needed to close the gap. The audit measures the shortfall and the true-up pays it down so the deployment becomes compliant.
By continuously tracking deployed versus licensed rather than reconstructing it under pressure when the vendor asks. Keep a live count of tags and seats per system, map every deployment to its covering license, and use the usage information many SCADA products expose to maintain a standing compliance picture. Assigning clear ownership of that figure prevents the slow, unwatched creep of tags and installations that turns an audit into an expensive discovery.
Because a gap found under audit is resolved from a weak negotiating position - the over-deployment already exists, so you are buying under pressure rather than planning a purchase on your own terms. The exact remedy depends on the specific agreement, but closing a gap under audit is generally less favourable than staying compliant or expanding deliberately. There is also the internal cost of the reconciliation effort and the operational risk of having relied on unlicensed capacity.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.