SAP Enterprise Agreement: Key Leverage Points

What the enterprise agreement governs

The SAP enterprise agreement is the master commercial document that governs the customer relationship. It sits above the individual product schedules and defines the terms that apply across all SAP products in the customer estate. The agreement is typically three to five years in duration and is the single document that has the largest impact on total cost of ownership over the contract period.

The enterprise agreement is also the document that customers most often sign without negotiating the structural clauses. Pricing receives the negotiation attention. The structural clauses receive less attention and routinely contain language that disadvantages the customer for the duration of the contract. The pillar coverage is in our cost optimization guide and our renewal negotiation guide.

Measurement clause

The measurement clause defines how SAP measures the customer estate, what tools are used, what windows apply, and what dispute mechanism exists. The default SAP language gives SAP wide discretion on measurement methodology and narrow dispute rights to the customer. The customer position should narrow the SAP discretion and broaden the dispute mechanism.

The specific language to push for includes a defined measurement window, a defined toolset, a defined evidence standard, and a defined dispute escalation path. The combination converts the measurement from a unilateral SAP exercise into a bilateral process with documented standards. Cross reference our LAW measurement guide and our findings dispute guide.

Indirect access clause

The indirect access clause is the single highest dollar exposure in most enterprise agreements. The default SAP language reserves broad rights to charge for indirect consumption based on assumed values. The customer position should narrow the indirect access definition, require measurement based on observable transactions, and exclude integration types that do not constitute consumption under the contract.

An indirect access clause that defines the consumption boundary in concrete terms removes the largest open ended commercial exposure in the SAP relationship. The clause is worth negotiating intensively even if the rest of the agreement is signed at the SAP starting position.

The detail of the indirect access framework is in our indirect access detection guide, our digital access conversion guide, and our indirect access expertise page.

Audit cooperation clause

The audit cooperation clause defines what data the customer must produce, on what timeline, and with what scope limits. The default SAP language requires broad cooperation on a tight timeline. The customer position should define the data scope, the production timeline, the working hours during which audit activity occurs, and the data handling standards that apply.

The cooperation clause should also define the limits on follow up audits. Without explicit limits, SAP can run sequential audits with overlapping scope. The customer position should require a minimum interval between audits and a defined scope boundary for each audit. Cross reference our audit timeline stages guide and our can you refuse an SAP audit coverage.

Exit and assignment clauses

The exit clause defines what happens at the end of the contract term. The default SAP language allows minimal customer flexibility. The customer position should preserve the right to terminate for convenience under defined conditions, the right to step down to a lower commitment level at renewal, and the right to terminate specific product lines without terminating the master agreement.

The assignment clause defines what happens when the customer entity changes through M and A activity. The default SAP language requires SAP consent to assignment, which creates a leverage moment for SAP at the customer M and A event. The customer position should preserve the right to assign in the context of corporate restructuring, divestitures, and acquisitions without triggering a renegotiation. See our M and A compliance pillar.

The full leverage map

The leverage map across the enterprise agreement contains roughly twelve clauses that materially shift customer position. Pricing escalation language, true up methodology, geographic scope, deployment model flexibility, currency and indexation, transfer rights between products, and the support service level definitions all sit in the second tier. Each clause individually is small. The combination across the contract period typically represents 15 to 25 percent of total cost of ownership.

The negotiation strategy should address the clauses in priority order, anchored on the customer evidence and the documented alternative scenario. See our volume discount tiers for the pricing structure framework and our license consulting service for the engagement model.