SAP License Audits Contact Us
Service VII · License Optimization

The licences you actually use.

Right-size the SAP estate. Reclassify user types. Retire shelfware. Rebuild the maintenance base. The annual saving lands on the next invoice cycle.

Contact Us → Read the Handbook
Optimization analytics workspace
Featured Engagement$4.2M annual maintenance trimmed from a $14M estate.
Client Savings
$180M+
across active SAP matters since 2018
Engagements Closed
500+
all SAP product lines, three continents
Average Reduction
68%
on the opening audit claim value
Practice Experience
20+
combined years inside SAP licensing
Section I · The Brief

The estate has drifted.

SAP estates accumulate. A user type chosen ten years ago is paid for forever. A divested business unit still holds its Professional seats. An engine licence acquired for a project that never went live continues to attract maintenance year after year. The estate grows, the operational use does not, and the maintenance line on the next invoice keeps increasing.

License optimization is the structured exercise of closing the gap. Across the engagements we have closed, the recurring annual saving has ranged from eight to thirty-five per cent of the SAP maintenance base. The work is technical, contractual, and procedural in roughly equal measure.

The optimization gap is also the audit gap. Every Professional seat that should be Limited is a finding waiting to happen. Every engine running below the licensed metric is recoverable spend. Every shelfware module is a maintenance line that the procurement team is paying for and the technical team is not using.

We work the estate before SAP works it. We classify users against actual transaction-code use. We rationalise engine metrics against measured throughput. We retire shelfware at the maintenance anniversary, within the limits the contract permits. We rebuild the licensing position from operational fact.

Section II · What's Included

Eight levers, one estate.

— I.

Entitlement Reconciliation

Full reconstruction of the licensing position from the master agreement, schedules, and order forms. The contractual baseline written down on one page.

— II.

User-Type Reclassification

Transaction-code analysis against the SAP Named-User catalogue. Professional, Limited Professional, Employee, Developer, ESS. The defensible classification per seat.

— III.

Engine Metric Rationalisation

Measured throughput against licensed metric. Payroll runs, order lines, HR records, document volumes. The engines you are over-licensed against, quantified.

— IV.

Shelfware Retirement

The modules you bought and never deployed. The seats you bought and never assigned. The maintenance reduction window, identified and executed.

— V.

Dormant-User Programme

The accounts that have not logged in for 180 days. The accounts that should be locked, deleted, or reclassified before the next measurement.

— VI.

Indirect-Access Modelling

The interface surface against the digital-access alternative. The two pricing models compared in writing, with the recommendation defended.

— VII.

Maintenance-Base Reset

The maintenance anniversary letter. The shelfware reduction request. The renegotiated maintenance base for the next contract cycle.

— VIII.

Continuous-Monitoring Playbook

The internal compliance dashboard. The classification rules. The change-control protocol so the optimised position does not re-drift before the next anniversary.

Section III · The Method

Four phases. Ten to fourteen weeks.

— Phase i.

Inventory

Entitlement reconstruction. Deployment topology. The licensing position written down on one page, against the operational reality.

— Phase ii.

Analyse

User-classification analysis. Engine-metric measurement. Shelfware identification. Indirect-access surface mapping. The recoverable spend, quantified.

— Phase iii.

Execute

Reclassification roll-out. Dormant-user lockdown. The maintenance anniversary letter. The shelfware reduction notice within the contractual window.

— Phase iv.

Sustain

Internal handover. Continuous-monitoring playbook. The position held across the next measurement cycle so the saving compounds rather than reverses.

— Featured Engagement · Optimization

The $14M estate trimmed to ten point one.

A European retailer carried fourteen point two million dollars in annual SAP maintenance against an estate built over twelve years of acquisitions, divestitures, and project starts.

We reclassified eighteen hundred Professional seats to Limited. We retired three engine modules at the maintenance anniversary. We reset the maintenance base at ten point one. The saving recurs every year of the agreement.

Read the case file →
Opening Base
$14.2M
annual maintenance, year zero
Optimised
$10.1M
annual maintenance, year one
Reduction
29%
on the recurring base
Duration
12wk
to the maintenance anniversary

Questions, frequently.

What is SAP license optimization?

SAP license optimization is the structured exercise of matching SAP licence entitlements to actual operational use. It covers user-type reclassification, engine-metric rationalisation, shelfware retirement, and maintenance-base reduction. It is the same exercise an SAP audit performs, conducted on your terms instead of theirs.

How much can an optimization exercise save?

In the engagements we have closed, the recurring annual saving has ranged from eight to thirty-five per cent of the SAP maintenance base. The precise figure is contract-specific. The first-pass estimate is delivered in week two.

Will SAP allow us to drop licences at renewal?

Most enterprise contracts permit a defined shelfware reduction at the maintenance anniversary, subject to procedural notice and contractual limits. The window and the mechanics are written in your agreement. The right notice in the right form is non-negotiable.

How long does an optimization engagement take?

Eight to fourteen weeks for the assessment phase, with the implementation timeline running into the next maintenance anniversary. The savings appear on the next invoice cycle and recur every year of the remaining agreement.

Does optimization create audit risk?

Done well, no. Optimization closes the gap between entitlement and use, which is the same gap an audit would otherwise identify. The work has to be defensible on its own terms, and our methodology is built around that defence.

Can you run optimization while an audit is active?

No. Optimization and audit defence are different engagements with different procedural rules. If a notification letter has arrived, the defence comes first. Optimization follows the settlement.

— Related research
White Paper

The SAP License Optimization Handbook

48 pages. The full optimization framework, from inventory to maintenance reset. PDF, gated.
Topic

SAP ECC licensing in 2026

The optimization opportunities in the ECC estate before the migration window closes.
Service

License Compliance Assessment

The diagnostic that precedes optimization. The defensible licensing position, written down.

The optimised estate is the audited estate.

Right-size the licensing position before SAP does. Speak with a specialist about the recoverable spend in your maintenance base.

Contact Us →