Last reviewed June 2026
A buyer-side playbook for the SAP audit: how USMM, SLAW, and LAW measurement works, how to reconcile named-user types, how the digital and indirect access lever operates, how to control scope and data, and how to settle a reconciled gap into a renewal or S/4HANA conversion.
An SAP audit is not an inventory count. SAP classifies named users and counts consumption with its USMM program, consolidates the result with SLAW or LAW, and asks you to submit it as a self-declaration. Most of the claim is decided before SAP ever sees a number.
This playbook is written for the buyers who fund SAP, not for the vendor that audits them. Every section ends with the buyer move and the discipline that keeps the declaration yours.
SAM and licensing teams responding to an SAP system measurement.
Procurement and vendor-management leads facing an SAP audit.
IT and enterprise architects mapping indirect and digital access.
Finance and legal teams sizing and settling audit exposure.
Across more than 500 enterprise engagements, buyers we advise have negotiated over $2.4 billion in software contracts, with average savings of 38 percent and average audit claim reductions of 72 percent.Atonement Licensing engagement record
Related resources: read the full playbook on the SAP Audit Defence & License Measurement Playbook page, then see our Vendor Audit Defence service and the SAP Indirect & Digital Access Playbook.
Instant access to the full playbook. No sales calls.
Weekly Oracle, Microsoft, SAP, and cloud licensing intelligence for enterprise buyers.
Our advisors represent buyers directly. Confidential assessment within one business day.