SAP Licence Audit · Audit Triggers · Enterprise Advisory

Top 10 SAP Licence Audit Triggers

Every enterprise running SAP should know what can trigger a licence audit. This advisory breaks down the top 10 red flags, from usage spikes and indirect access to M&A events and third-party support transitions, with practical ITAM strategies to stay ahead.

SAP Audit Defence Book a Consultation
Call us: +1 (239) 402-7397
Every 2-3 yrs
Typical audit frequency for large SAP customers
22%
Annual maintenance on licence fees (back-dated in audits)
$54M+
SAP v Diageo indirect access ruling
10
Key red flags covered in this advisory
SAP Hub SAP Audit Survival Guide Top 10 SAP Licence Audit Triggers

This advisory is part of our SAP Licensing Knowledge Hub. For the complete audit defence guide, see SAP Licence Audit: A Survival Guide.

Top 10 SAP Audit Triggers

SAP often zeroes in on certain red flags that signal potential non-compliance. Understanding these triggers, and preparing for them proactively, is the most effective way to avoid audit surprises and unbudgeted true-up costs.

1
Sudden usage spikes. A rapid increase in SAP usage, onboarding hundreds of new users or a surge in transactions, raises concern that you have outgrown your entitlements. SAP monitors utilisation; a sharp spike in user count or data volume is a classic trigger. Track user counts internally. Run SAP's LAW tool after major expansions. Inform your SAP account team when planning large rollouts.
2
Contract renewals and true-ups. Approaching a licence renewal or scheduled true-up is prime time for an audit. SAP often audits right before negotiations to establish a usage baseline, ensuring any extra consumption is paid for in the new contract. Perform a full internal audit before any renewal. Enter negotiations knowing exactly where you stand.
3
New modules or system expansions. Deploying SAP HANA, a CRM add-on, a cloud connector, or any new component triggers a compliance check. SAP views new implementations as points of risk. Treat every new implementation as a licensing event. Consult your contract before enabling modules. Run measurement tools after deployment.
4
Mergers, acquisitions, or divestitures. M&A events create double-counting and licence confusion. When companies merge, the combined user base changes significantly. SAP frequently audits after M&A to reconcile licensing under the new organisation. Engage licence management early in any M&A. Inventory SAP systems and users as they come and go.
5
Indirect access and third-party integrations. Non-SAP applications interacting with SAP data, CRM pulling customer info, e-commerce creating sales orders, require additional licences even if no one logs into SAP directly. The SAP v Diageo case ($54M+ for unlicensed indirect usage) made this a headline risk. Map all third-party interfaces. Evaluate SAP's Digital Access (document-based) licensing. Negotiate contract language clarifying indirect use.
6
Long gap since last audit. SAP can audit annually, but typically audits large customers every 2-3 years. If it has been a long time since your last review, that alone puts you on SAP's radar. Usage drift, gradual user growth or data expansion, accumulates silently. Always assume an audit is coming. Maintain annual internal reviews.
7
Past audit findings or compliance history. Customers with prior shortfalls are considered high-risk accounts. If your last audit resulted in a true-up purchase or misclassification finding, SAP will follow up in subsequent years, potentially with an enhanced (deeper) audit. Remediate root causes immediately after any audit finding.
8
Missing or inaccurate licence data. Failing to submit LAW data on time, sending incomplete reports, or showing a high number of "unclassified" users signals lack of control. Ignoring a measurement request almost guarantees an audit notice. Run the latest measurement programmes across all systems before deadlines.
9
Switching to third-party support. Leaving SAP maintenance for a third-party provider increases audit risk. An audit may be SAP's last opportunity to enforce compliance and potentially collect back-support fees. Many companies report audit notices within 1-2 years of switching. Conduct a thorough internal audit before discontinuing SAP support.
10
Staying on legacy SAP software. Delaying migration to S/4HANA or SAP cloud products attracts audit attention. SAP's sales strategy pushes customers to the latest platforms. As the 2027 ECC support deadline nears, long-time ECC customers face increasing compliance pressure. Even in a holding pattern, optimise licence usage continuously.

Critical risk alert: indirect access. Indirect access remains the single most expensive audit finding. The landmark SAP v Diageo ruling, where a customer was charged over $54 million for unlicensed indirect usage via third-party systems, demonstrated the scale of risk. SAP's Digital Access model was introduced to address this, but many customers remain unsure of their exposure. Map all interfaces and evaluate Digital Access licensing before SAP does it for you.

SAP User Licence Types: Costs and Compliance Risk

Misclassifying users is a common audit finding. The cost differences between licence types illustrate why SAP auditors focus heavily on correct classification.

User Licence TypeApprox. CostIntended UsageRisk If Misused
Professional User$3,000-$4,000 + 22%/yrFull access to all SAP modules (power users)Under-licensing if a heavy user is given a lower licence type
Limited Professional$1,500-$2,000 + 22%/yrRestricted scope (specific modules or tasks)If user performs tasks beyond the limited scope, Professional licence required
Employee Self-Service$500-$1,000 + 22%/yrSelf-service tasks only (time entry, HR self-service)Using ESS users for regular operational work violates terms
Developer User~$1,000 + 22%/yrDevelopment and configuration (non-production)If developer accounts execute business transactions in production, Professional licence also required

User misclassification is a common "gotcha." Any account without a licence type assignment defaults to the most expensive category. Upgrading a misclassified user from a $1,000 licence to a $3,000 licence, plus back-maintenance, multiplied across dozens of users creates a substantial bill. ITAM teams should regularly review user roles and licence assignments to ensure each user has the correct type.

Recommendations

#RecommendationPriority
1Conduct regular self-audits. Schedule internal licence compliance reviews at least annually. Use SAP's LAW tool to check user counts, classifications, and engine usage.Critical
2Optimise licence assignments continuously. Lock/remove inactive users, consolidate duplicates, and right-size every user's licence type.Critical
3Monitor indirect usage proactively. Inventory all third-party systems and integrations interacting with SAP. Consider SAP Digital Access licences for document-generating integrations.Critical
4Engage SAP early for big changes. M&A, new modules, cloud migrations. Proactively updating contracts prevents audits later.High
5Leverage contract clauses. Negotiate 60-day notice, max one audit per year, and the right to remedy shortfalls at your discount (not list price).High
6Train and communicate. Make SAP compliance a team sport. Train technical teams, project managers, and procurement on audit triggers.High
7Keep excellent records. Central repository of all SAP contracts, licence certificates, purchase orders, and correspondence.Moderate
8Budget a compliance cushion. Earmark a small contingency for true-ups.Moderate
9Consider expert support. For high-stakes audits, engage independent SAP licensing specialists. They often save far more than their cost.Moderate
10Foster a compliance culture. Include licence impact in change management processes and cloud transition plans.Moderate

The best audit defence is being audit-ready at all times. Organisations that maintain annual internal reviews, clean user lists, and documented entitlements can respond to an SAP audit notice within days, not weeks. This confidence translates directly into better negotiation outcomes: you negotiate from facts, not fear.

ITAM Action Checklist: SAP Audit Readiness

1. Set up an internal audit calendar. Mark a date (at least yearly) to run SAP's user measurement reports and review licence usage. Treat it like a mini-audit. Identify overshoot in users or engines before SAP does.
2. Clean your SAP house. Purge or fix obvious compliance issues immediately. Remove dormant users, correct licence classification errors, reconcile engine metrics. Document all clean-up actions.
3. Brief stakeholders on audit triggers. Hold a session with ITAM, SAP Basis, procurement, and project teams on the top 10 triggers. Ensure everyone knows that adding a new module or integrating a new app involves a licensing check.
4. Review contracts for audit terms. Check the audit clause and true-up provisions. If anything is vague or one-sided (no notice period, unclear scope), prepare to address it at next negotiation.
5. Simulate an audit response. Assemble your "audit response" team. Generate a LAW report, compile user lists, and map them to entitlements. This dry run reveals weak spots in data quality before a real audit exposes them.

Frequently Asked Questions

How often does SAP audit enterprise customers?
+

Most large SAP customers can expect a licence audit roughly every 2-3 years. SAP can audit annually under its contract, but does not always exercise this right. However, self-reviews via SAP's measurement tools happen yearly. If you have not been audited in a long time, assume you are due, especially if any trigger events have occurred.

What is the difference between SAP's "basic" and "enhanced" audit?
+

A basic audit is largely routine: SAP asks you to run their standard measurement programmes (USMM and LAW) and provide the results. An enhanced audit is more intense: SAP's auditors dig deeper with detailed questionnaires, remote sessions, or on-site visits. Enhanced audits occur if SAP suspects significant compliance issues such as extensive indirect use or past problems.

Can we negotiate or refuse an SAP audit?
+

You cannot refuse an audit, it is a contractual right SAP holds. However, you can negotiate timing and scope. If the proposed period coincides with a critical business quarter, you might request a deferral. Always respond professionally, confirm compliance intent, but request reasonable accommodations in writing. If SAP requests something outside the agreed scope, you can push back using your contract terms.

What are the biggest "gotchas" auditors find?
+

Common findings include: unassigned users (accounts without a licence type default to the most expensive category), misclassified users (users doing more than their licence allows), indirect usage (systems creating SAP transactions without proper licences), engine overuse (exceeding licensed metrics), and developer misuse (using developer accounts for production transactions). Auditors also flag duplicate accounts and inactive users consuming licences.

If an audit uncovers shortfalls, how much will it cost?
+

You would typically need to purchase licences for any shortfall at list price, plus back-dated maintenance (22% per year for each year of unlicensed use). For example, 50 under-licensed Professional Users for 2 years means full-price purchases plus 2 years of maintenance on each. SAP generally does not levy fines beyond licence fees, but without prior arrangements you will not get your negotiated discount. Negotiating a cap or discount on audit findings in your contract is highly valuable.

Related Resources

Service
SAP Licence Optimisation
Service
SAP Audit Defence
Service
SAP Digital Access Advisory
Service
SAP Contract Negotiation
Service
RISE with SAP Advisory
Knowledge Hub
SAP Licensing Knowledge Hub
FF

Fredrik Filipsson

Co-Founder, Redress Compliance

Fredrik Filipsson brings over 20 years of experience in enterprise software licensing, having worked directly for IBM, SAP, and Oracle before co-founding Redress Compliance. Over the past 11 years as an independent advisor, he has helped more than 500 enterprise clients, including numerous Fortune 500 companies, optimise costs, avoid compliance risks, and secure favourable terms with major software vendors.

← Back to SAP Knowledge Hub