SAP Audit Findings: Common Issues and How to Dispute

Findings are not facts

An SAP audit finding is an SAP position. It is not a fact. It is a position that SAP will negotiate, refine, or withdraw based on the evidence the customer produces and the contractual interpretation the customer asserts. Customers who treat the finding as the final position have already conceded the negotiation. Customers who treat the finding as an opening position routinely settle for a fraction of the initial demand.

This article describes the seven finding categories that account for more than 80 percent of the audit findings observed across our Fortune 500 engagements. Each category has a recurring methodology error, a recurring dispute pattern, and a typical settlement reduction. The framework that sits behind this article is in our SAP license audit complete guide and our audit defense expertise page.

Finding one: user misclassification

The most common finding category is user misclassification. SAP asserts that users classified as Limited Professional or Employee in LAW should be reclassified as Professional based on observed authorization or observed activity. The aggregate value of the reclassification frequently exceeds tens of millions of dollars for a Fortune 500 customer.

The dispute framework rests on three pillars. The contractual definition of each user type. The authorization analysis that demonstrates the user falls within the contracted user type. And the activity analysis that demonstrates the user does not exercise authorization beyond the contracted user type. The detail is in our named user reclassification guide and the named user license types reference.

Finding two: indirect access exposure

Indirect access findings have become the highest dollar value finding category over the past five years. SAP applies the Digital Access estimator across a broad transaction set and produces a document count that, multiplied by document pricing, generates a finding that frequently exceeds 30 percent of the total audit value.

The dispute framework rests on four pillars. The contractual scope of indirect access. The trigger transaction definition. The document count methodology. And the Digital Access pricing applicability. Most indirect access findings are reduced by 50 to 75 percent through the dispute process. Cross reference our indirect access explainer, the digital access document pricing analysis, and the indirect access expertise page.

Finding three: engine metric calculation

Engine metric findings cover the per engine consumption results from LAW. SAP asserts engine consumption that exceeds the contracted engine entitlement. The most common errors are engine inclusion of populations that are contractually excluded, engine metric definitions that differ from the contractual definition, and engine measurement periods that do not align with the contractual measurement period.

The dispute framework rests on the engine specific contractual clauses and the engine specific metric definitions. Engine findings are highly engine dependent. Payroll engine findings dispute differently from HR engine findings, which dispute differently from financial transaction engine findings. The detail by engine is in our engine based licensing guide.

Engine findings are frequently overlooked in dispute preparation because they appear less contestable than user findings. In practice engine findings dispute as effectively as user findings because the contractual definitions are typically narrower than the SAP standard definitions.

Finding four: scope creep

Scope creep findings appear when SAP measures products that are not on the contract, time periods that exceed the contractual retention, or affiliates that are not within the contractual customer definition. Scope creep findings are procedurally invalid. They are findings against an audit scope that the contract does not authorize.

The dispute framework on scope creep is the contractual audit clause. The audit clause defines the products, the time period, and the affiliates that are within audit scope. Findings outside this scope are withdrawn upon procedural objection. The detail is in our audit rights contractual analysis and the scope confirmation playbook.

Finding five: legacy product allocation

Legacy product findings appear when SAP asserts that legacy product entitlements have been converted into newer product entitlements at lower conversion ratios than the contract supports. The conversion economics typically favor the SAP position by a factor of two to five. The dispute framework rests on the contractual conversion clauses, the historical product entitlement records, and the contractual product equivalence statements.

Legacy findings are common in long tenured SAP customers and in customers that have migrated from ECC to S/4HANA without explicit license conversion. Cross reference our S/4HANA licensing pillar and the S/4HANA conversion economics analysis.

Finding six: documentation gaps

Documentation gap findings appear when the customer cannot produce contractual entitlement documentation that supports the customer position. The documentation that SAP requests typically exceeds what the contract requires the customer to maintain. The dispute framework rests on the contractual documentation obligations and the burden of proof allocation in the audit clause.

Most contracts place the burden of proof on SAP, not the customer. SAP must demonstrate the finding. The customer is not obligated to disprove every SAP assertion. Customers who understand the burden allocation reduce documentation gap findings to near zero. Cross reference our audit documentation guide.

Finding seven: timing and rounding

Timing and rounding findings appear when SAP measures peak usage across the measurement period rather than average usage, applies penalty multipliers that the contract does not authorize, or aggregates affiliate usage in a manner that exceeds the contractual aggregation method. The dispute framework rests on the contractual measurement methodology and the contractual rounding conventions.

Timing findings frequently produce 10 to 20 percent of the audit value and are commonly overlooked in dispute preparation. The contractual rebuttal is typically clean and produces full elimination of the finding. Cross reference our audit data collection guide, the license consulting service, and the license optimization expertise.