SAP audits read against the buyer's measurement, contract and remediation evidence. The Admodum read on the audit-clause perimeter, the four published findings, the rehearsal discipline, the settlement framework.
The SAP audit reads against the audit clause in the enterprise agreement. The clause sets five perimeters. The notice-period perimeter sets the minimum notice the publisher must give before the audit window (typically thirty days, sometimes sixty). The window perimeter sets the period the audit may read against (typically the prior two contract years, sometimes a shorter look-back). The entity perimeter sets the legal entities the audit may read against (the named principal entity and the named Affiliated Entities, against the contracted Affiliate definition). The system perimeter sets the SAP systems the audit may read against (the named productive systems, the named non-productive systems, the named development and test systems). The user-population perimeter sets the user populations the audit may read against (the employees, the named contractors, the named third-party access populations).
The contractual audit clause is the perimeter; the publisher's standard audit script is not. The wider SAP system measurement spoke reads the measurement protocol that operates inside the perimeter. The wider named-user recategorisation spoke reads the buyer-side audit move on the named-user surface.
The four published findings of an SAP audit are well-rehearsed by the publisher's audit team. The first is the named-user finding: the categories-versus-licences delta, where the audit reads each user's activity against the licensed category and produces an over-classification position (or, less commonly, an under-classification position). The second is the engine-metric finding: the metric-base-versus-contracted-metric delta, where the audit reads the actual chargeable order count, PO line count, patient-day count or other engine metric against the contracted metric base. The third is the Digital Access finding: the connected-systems-versus-document-licence delta, where the audit reads the nine-document-type flow from non-SAP systems against the Digital Access licence position. The fourth is the contract-perimeter finding: the in-scope-versus-out-of-scope entity reading, where the audit tests whether the contract permits the use of the SAP digital core by the affiliates, joint ventures or divested business units that are accessing it.
The four findings are independent: a clean named-user position does not protect against an engine-metric finding; a clean engine-metric position does not protect against a Digital Access finding. The wider Digital Access explained spoke reads the third finding in depth; the wider indirect access history spoke reads the historical evolution of the Digital Access reading.
The rehearsal discipline produces the buyer-side position-of-record ahead of the audit window. The rehearsal runs the same USMM-LAW-SLAW protocol that the publisher will run, against the same user inventory, at a point ahead of the published audit window. The rehearsal output is the position the buyer will present at the audit window. The recategorisations, the cleared inactive accounts, the reconciled engine-metric readings and the Digital Access classifications are already applied in the rehearsed output; the audit then reads against the rehearsed position, not against the unprepared estate.
The rehearsal typically runs eight to twelve weeks ahead of the published audit window (longer than the renewal-time rehearsal, because the audit window has the look-back perimeter and the historical evidence has to be reconstructed). The remediation work runs in parallel: the named-user remediation (the inactive-account clearance, the over-classified user recategorisation, the duplicate-account consolidation), the engine-metric remediation (the metric-base correction), the Digital Access remediation (the connected-system review), the contract-perimeter remediation (the affiliated-entity reconciliation against the contracted Affiliate definition).
The publisher's audit team operates against a standardised script: the script runs the USMM-LAW-SLAW protocol, applies the publisher's current product-term category definitions (not the buyer's contracted category definitions, which may be from an earlier product-term version), reads the engine-metric base against the publisher's current metric definitions, and reads the connected systems against the publisher's current Digital Access classification. The script is not the contractual perimeter; the contract is. The contractual category definitions, the contractual engine-metric definitions, the contractual Digital Access scope (or its predecessor indirect-use clause) and the contractual entity perimeter are the position-of-record.
The reconciliation runs four streams. The first is the category definition: the buyer's contracted category set is the position-of-record, against the contract anniversary. The second is the engine-metric definition: the buyer's contracted metric base is the position-of-record. The third is the Digital Access classification: the buyer's contracted indirect-use clause (or, post the Digital Access overlay, the buyer's contracted Digital Access scope) is the position-of-record. The fourth is the contracted Affiliate definition: the buyer's contracted Affiliated Entity scope is the position-of-record.
The settlement framework has four published outcomes. The first is the zero-finding outcome: the rehearsed position holds, the publisher-side audit output reads back against the rehearsed position, no settlement is required. The second is the in-perimeter settlement at the contracted price: the deficit is closed at the buyer's contracted price level (the contracted price-list level, not the publisher's current list-price level), with the published terms applying to the closure. The third is the renewal-overlay settlement: the gap is rolled into the next renewal commitment, with the renewal discount applied to the gap as well as to the new entitlement, against staged timing through the audit-clause window. The fourth is the credit-as-discount outcome: the gap is written off against a forward commitment (a RISE conversion commitment, a BTP overlay commitment, an Ariba Network or SuccessFactors expansion), with the credit valued at the price level of the displaced spend, not at the published list price of the credited items.
The wider SAP renewal cycle spoke reads the renewal-side reconciliation; the wider RISE versus on-prem spoke reads the credit-as-discount disposition on a RISE forward commitment.
At the close of the audit, the buyer holds five artefacts. The first is the audit-output read against the rehearsed position-of-record. The second is the contracted-perimeter reconciliation against the publisher's audit-script perimeter. The third is the settlement outcome (zero-finding, in-perimeter settlement, renewal-overlay or credit-as-discount). The fourth is the settlement-instrument record (the contract amendment, the renewal addendum, the credit-and-discount letter). The fifth is the audit-window closure (the published certification that the audit cycle for the prior two contract years is closed, with the next eligible audit window not earlier than the next contracted audit-notice period).
The wider engagement sits in the SAP practice; the aggregated reading list sits in the SAP knowledge hub; active audit moments route to Audit Defence; active renewal moments route to the Renewal Programme.
The USMM-LAW-SLAW protocol that operates inside the audit-clause perimeter.
A senior Admodum SAP advisor will read your audit-clause perimeter, your rehearsed measurement, your reconciled engine-metric base and your Digital Access classification on a private call. Active audit moments route to Audit Defence.