① Journal · Software AG · Audit
Software AG audits concentrate on the legacy Adabas and Natural estate, where contracts signed years ago meet deployments that have quietly grown. From the buyer side the leverage often sits in the contract language itself, which is exactly why reading it first matters more here than almost anywhere else.
A Software AG audit reads an old contract against a current estate. Read it before they do.
Software AG (the Adabas and Natural business, now a standalone unit under private equity ownership) licenses two long lived mainframe estates that sit at the core of many enterprises. Adabas, the database, and Natural, the application language, are frequently governed by contracts signed years or even decades ago and rarely revisited since. That is the condition a Software AG audit tests. The capacity or processor metric for Adabas, the user and processor counts for Natural, the separately licensed gateways and add-on modules that surround the core products, and the terms buried in the original agreement. The activity we observe concentrates on the gap between an old contract and a current deployment, because on a mission critical estate that nobody renegotiates, scope drifts and the buyer rarely tracks it.
The pattern we commonly observe is a reconciliation the buyer can actually win, but only if the contract is understood first. Legacy agreements on these products often carry vague scope, uplift clauses, and territory or entity restrictions that cut both ways. Separately licensed gateways and options are easy to deploy and easy to lose track of. The capacity basis may have been set against hardware long retired. The buyers who come through a Software AG audit without a surprise are the ones who reconciled the capacity and user basis against deployment, inventoried every gateway and add-on, and read the legacy contract terms before responding, so they knew the scope and any caps before Software AG framed them. Read this with our Adabas and Natural audit defense guide and the Software AG publisher hub.
Where Software AG audits cluster · what we commonly observe and the buyer defense
| Focus area | What Software AG checks | Buyer defense |
|---|---|---|
| Adabas capacity metrics | Capacity or processor basis for the database against deployment | Validate the metric basis, reconcile to where it actually runs |
| Natural user and CPU counts | User populations and processor scope for Natural | Reconcile active users and processors, retire dormant access |
| Gateway and add-on entitlement | Separately licensed gateways, options, and add-on modules | Inventory every option, match each to entitlement |
| Legacy contract terms | Aging contracts with vague scope, uplift, and territory clauses | Read the legacy terms and caps before you respond |
These are patterns we commonly observe across Software AG audits of Adabas and Natural, not statements of Software AG audit policy. Your specific entitlements, contract scope, and metrics govern; validate against your own records and your agreement before relying on any position.
An Adabas and Natural audit turns on the metric, and the metric is often set against conditions that no longer hold. Reconcile the Adabas capacity basis against where the database actually runs, count active Natural users and processors against the licensed scope, and retire dormant access before it is counted for you. A basis you have validated is a basis you can defend. See our explainer on capacity metrics.
Validate the metric before the auditor reads it.
The core products are surrounded by separately licensed gateways, options, and add-on modules that are easy to deploy and easy to forget. Inventory every option actually in use, match each to a specific entitlement, and document anything decommissioned. The quiet exposure on a Software AG estate usually lives in these add-ons rather than the core database itself. A clean inventory is a clean reconciliation.
The add-ons are where the surprise hides.
On these estates the leverage often sits in the contract language. Read the original agreement before answering anything, because the scope definition, any uplift caps, and territory or entity restrictions shape what Software AG can actually claim. A buyer who knows the terms negotiates the reconciliation from the contract rather than from the vendor's framing of it. See our guide to Adabas and Natural audit defense.
The contract is the leverage. Know it first.
④ Where the Software AG audit is won
A Software AG audit reads an old contract against a live estate. The defense is reading it first. Validate the basis, inventory the add-ons, know the contract.
Mobilization on an audit notice
Mainframe spend negotiated on the buyer side
Typical renewal reduction
The legacy Adabas and Natural estate: capacity and processor metrics for Adabas, user and processor counts for Natural, entitlement for the separately licensed gateways and add-on modules, and the terms in aging contracts that often carry vague scope, uplift, and territory clauses. The common thread is an old estate where the contract and the deployment have drifted apart.
These are long lived estates, frequently licensed under contracts signed years or decades ago and rarely renegotiated since. The business now operates as a standalone unit under private equity ownership with a continued release roadmap. Long lived contracts on mission critical systems with separately licensed add-ons are a natural audit focus, because scope drifts and the buyer rarely revisits the original terms.
Treat it as a reconciliation against contracts you should read first. Reconcile the capacity and user basis against deployment before sharing anything, inventory every gateway and add-on against entitlement, read the legacy terms so you know the scope and any caps, and answer each request in writing scoped to the products in question. The leverage on a legacy estate often sits in the contract language. See what happens to pricing after a vendor is acquired.
We reconcile the capacity and user basis, inventory the gateways and add-ons, read the legacy contract for scope and caps, and manage the response from the buyer side so the reconciliation runs on your evidence. Our audit defense service mobilizes within 48 hours of a notice and our license negotiation service resets the terms the audit and the next renewal build on.
Related: Software AG publisher hub · Adabas and Natural audit defense · IBM audit activity · Broadcom (CA) audit activity · audit defense
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →