The compliance KPI framework — seven measures

A compliance programme that cannot be measured drifts. The KPI framework is the discipline that converts an SAP licence-compliance function from a periodic firefighting exercise into a managed programme with defined inputs, defined outputs, and defined performance against a board-reportable standard. This article describes the seven KPIs that we apply across compliance engagements, the data sources behind each, the target ranges, and the reporting cadence that keeps the framework live.

Why a KPI framework

SAP licence compliance is, in most estates, run as an event-driven function: the audit lands, the team responds, and the discipline stands down until the next event. The pattern produces three predictable failure modes. The compliance posture drifts in the periods between audits and is rebuilt under duress when the next audit arrives. The institutional memory of the prior settlement is not converted into operational metrics that prevent the same finding recurring. And the licensed-cost trajectory of the estate is not visible to the procurement or finance function that funds it. The KPI framework closes those gaps. The framework is the standing instrument of a managed compliance programme, run quarterly against the data sources already in the audit data room.

The seven KPIs

The framework runs on seven KPIs. Each has a defined data source, a defined formula, and a target range based on the cross-engagement benchmarks we have collected. The seven, taken together, capture the operational health of the compliance function in one page of report.

KPI 1: Named-user occupancy ratio

The ratio of assigned named-user entitlements to active users in the trailing ninety-day window. The target range is between 1.05 and 1.15. A ratio below 1.05 is under-provisioned and risks operational friction; a ratio above 1.15 is over-provisioned and represents shelfware. The remediation, where the ratio is high, is harvesting and re-allocation; the methodology is in the pool-rebalancing article.

KPI 2: Category-mix index

The proportion of the active named-user inventory in each licensing category, indexed against the consumed-category mix derived from usage telemetry. The target is convergence between the assigned mix and the consumed mix. A divergence above ten percentage points in any single category is the signal for a rebalancing cycle. The methodology is in the named-user buckets article.

KPI 3: Digital Access utilisation

The ratio of chargeable documents in the trailing twelve months to the contracted Digital Access tier, expressed as a percentage of tier capacity. The target range is sixty to eighty per cent. Above eighty per cent the estate is approaching a true-up event and the next tier should be modelled. Below sixty per cent the entitlement is over-bought and the next renewal should re-negotiate downward.

KPI 4: Indirect-use coverage

The proportion of measured indirect-use activity covered by the active contractual posture — either Digital Access entitlement, named-user coverage, or a contractually defined carve-out. The target is one hundred per cent. Any gap is the residual indirect-use exposure that drives most large audit-time findings. The methodology is in the middleware risk article.

KPI 5: Engine-metric utilisation

The ratio of measured consumption to entitlement for each engine-priced metric in the estate — payroll runs, order-management lines, BW data volume, and the rest. The target range is between sixty and ninety per cent. The KPI separates the engines that are under-utilised (potential downsize at renewal) from those approaching capacity (potential true-up). The methodology is in the engine-metric white paper.

KPI 6: Audit-readiness score

A composite score, ranging zero to one hundred, that captures the completeness of the audit data room across its six artefacts. The target is ninety or above. The score is calculated by a defined rubric — presence, currency, methodological documentation — and reviewed quarterly. The methodology is in the audit data room article.

KPI 7: Renewal-window forecast

The projected licensed-cost trajectory of the estate at the next renewal event, modelled against the current measurement, the projected growth, and the open negotiation positions. The forecast is the input to the procurement budget and the leverage planning for the renewal. The methodology is in the renewal timing article.

The reporting cadence

The KPI framework runs on a quarterly reporting cadence aligned to the SAP system measurement cycle. The deliverable is a one-page dashboard with the seven KPIs, the trailing-four-quarter trend, the target range, and a short commentary on any KPI outside its range. The dashboard is the artefact that goes to the procurement steering committee and, in mature programmes, to the audit committee of the board. The discipline is that the dashboard is produced regardless of the operational state of the estate; the audit-time defensibility of the programme depends on the consistency of the measurement.

The data sources

The seven KPIs draw on four data sources, all of which are already maintained in the audit data room. The named-user inventory from USR02 and the role assignment tables, joined with usage telemetry from ST03. The Digital Access baseline from the document-counting methodology. The engine-metric measurement from the relevant system tables. And the contractual extract for the entitlement reference data. The KPI framework adds no new data extraction; it is an analytical overlay on the data the data room already produces. The compliance assessment service page describes the engagement structure.

The target ranges

The target ranges in the framework are derived from cross-engagement benchmarks across the estates we have measured. They are not absolute: the optimal range for any given estate depends on its operational profile, its growth trajectory, and its contractual posture. The discipline is to set the local targets explicitly at the start of the programme, to review them annually, and to hold the measurement methodology consistent between reviews so that the trailing trend is meaningful. The licence-optimization framework white paper covers the broader benchmarking landscape.

What the framework achieves

An estate that runs the seven KPIs quarterly accumulates three benefits over an estate that does not. The licensed-cost trajectory is visible and forecastable, so the procurement function can plan against it. The audit-time response is faster and more defensible, because the KPIs are themselves the operational summary of the data room. And the recurring rebalancing, harvesting, and renewal-negotiation cycles are run against a documented baseline rather than against a periodic snapshot. Across our engagements, the seven-KPI discipline correlates with licensed-cost savings of eight to fifteen per cent in the first year and three to seven per cent in each subsequent year.

The global-manufacturer case file documents one engagement where the KPI framework was the operational backbone of the broader programme.

Where to start

For an SAM or procurement team that wants to introduce the framework over the next quarter, the practical starting point is the audit-readiness score — KPI 6. Building the score forces the completion of the audit data room, which is the prerequisite for the other six KPIs. With the data room in place, the remaining six KPIs run on three to five analyst-days per quarter. The first dashboard goes to the steering committee at the end of the second quarter. The full operational benefit of the framework lands in the second year of the programme, by which point the trailing trend is meaningful and the renewal-cycle forecast carries forecasting weight. The S/4HANA topic page covers the equivalent discipline for estates in active migration.

The maturity curve

A KPI framework introduced into an estate that has run compliance as an event-driven function moves through a predictable maturity curve. In the first two quarters the dashboard is incomplete, several KPIs sit outside their target range, and the audit-readiness score is below sixty. In quarters three and four the data room reaches operational quality and the seven KPIs converge inside their ranges. In year two the trailing trend is meaningful, the renewal-window forecast carries forecasting weight, and the compliance posture is visible across the trailing four quarters with documented variance commentary. The audit-time defensibility of the programme improves at each step of the curve, with the largest single uplift between the second and third quarter, when the data room first reaches operational quality.

The discipline that holds the curve on track is the named ownership of each KPI by a single accountable individual, the version-controlled methodology, and the quarterly review with the procurement steering committee. Without those three governance elements, the framework drifts back into an event-driven posture inside twelve months. With them, it becomes the operational backbone of the licensing relationship.