SAP global agreements. GAP, GVL, and the strategy.

SAP global license agreements consolidate multi entity, multi region enterprise spend into a single commercial vehicle. The Global Agreement Program (GAP) provides the legal framework. The Global Volume License (GVL) provides the discount mechanism. Customers running 30 plus countries and 50 plus legal entities use both. The combination delivers procurement simplification and material discount, when the strategy is right.

The mistake pattern is consistent. Customers accept the default entity scope SAP proposes, miss the FUE conversion exposure that S/4HANA transitions create, and discover indirect access requirements only after the GAP is signed. The result is a global vehicle that locks in pricing for three to five years at suboptimal terms.

This article maps the GAP and GVL structures, the entity scope decision, the currency and indexation mechanics, the indirect access exposure, the FUE conversion math, the RISE inclusion decision, and the renewal posture. Run it alongside the SAP RISE negotiation guide and the SAP RISE TCO calculator.

GAP versus GVL

The two SAP global vehicles serve different commercial purposes. Understanding the split is the foundation for the negotiation strategy.

GAP and GVL side by side

Element	GAP (Global Agreement Program)	GVL (Global Volume License)
Purpose	Legal framework consolidating multi entity contracts	Commercial discount mechanism based on aggregate commit
Term	Three to five years	Aligned to GAP term
Eligibility	Typically 25M USD plus annual SAP spend	Typically 10M USD plus annual SAP spend
Entity coverage	Master agreement with country adden- da	Volume aggregation across covered entities
Discount mechanism	None directly. Provides the contract vehicle.	Tiered discount on the total commit value
Renewal	Multi entity renewal in one cycle	Renewal pricing references the original commit

When each vehicle applies

• GAP only. Multi entity simplification without aggressive discount expectations.
• GVL only. Single entity, single country, large spend.
• GAP plus GVL. Multi entity enterprises with 10M USD plus annual SAP spend. The standard for the Fortune 500.

Entity scope

The entity scope decision is the single biggest determinant of the GAP economics. Customers tend to default to global inclusion because SAP positions it as the simplifying choice. The buyer side discipline is to define scope intentionally.

The entity scope framework

1. Inventory the legal entities. Parent, subsidiaries, joint ventures, divested entities.
2. Map SAP footprint by entity. Which entities run SAP today. Which will adopt SAP.
3. Identify carve out candidates. Entities with potential divestiture or transition.
4. Define the GAP entity scope. Include only entities with stable SAP commitment.
5. Negotiate the addition mechanism. How new entities join the GAP after signing.
6. Negotiate the removal mechanism. How divested or transitioned entities exit the GAP.

The over scoping trap

A customer that places every legal entity under the GAP at signing loses the optionality to carve out divested entities or to negotiate separate terms for entities with different SAP footprints. Two years later, when the customer divests a subsidiary, the SAP contract for that subsidiary cannot be transferred or canceled. The customer pays for SAP licenses tied to entities no longer operating.

Currency and indexation

Multi currency exposure is unavoidable in a global SAP deal. The customer with operations in EUR, USD, GBP, JPY, and INR pays SAP across all those currencies. The GAP defines the currency conversion mechanism.

Currency conversion options

• Locked at signing. Conversion rate fixed at the GAP signing date. Customer hedges against currency movement.
• Floating at invoice. Conversion at the rate prevailing on each invoice date.
• Annual reset. Conversion locked annually at the anniversary date.
• Quarterly average. Conversion at the rolling quarterly average of the prevailing rate.

Price indexation

The GAP typically includes a price indexation clause that allows SAP to adjust local currency prices for inflation or currency movement. The customer should negotiate the indexation formula. Hard caps on both annual and cumulative indexation across the term prevent surprise increases.

Indirect access

Indirect access is the SAP licensing requirement triggered when non SAP applications read SAP data. The 2018 Digital Access framework introduced document based pricing for indirect access. The GAP does not change the indirect access definition.

Indirect access discovery

1. Inventory third party applications integrated with SAP. List every system, including custom integrations.
2. Identify the integration pattern. Read only, read write, document creation.
3. Measure the volume. Documents per year, users involved, data flows.
4. Map to SAP Digital Access categories. Sales document, purchase document, financial document, etc.
5. Calculate the Digital Access licensing requirement. Documents per year times rate per document.
6. Negotiate the Digital Access framework into the GAP. Volume bands, rate locks, indirect access waivers where appropriate.

FUE conversion

FUE (Full User Equivalent) is the SAP S/4HANA Cloud user metric that converts existing on premise named user counts into S/4HANA Cloud user counts. The conversion ratio varies by user type and drives the S/4HANA Cloud commit value.

FUE conversion ratios

SAP on premise user type	S/4HANA Cloud FUE conversion
SAP Professional User	1.0 FUE
SAP Limited Professional User	0.2 to 0.5 FUE
SAP Functional User	0.5 FUE
SAP Employee User	0.05 to 0.2 FUE
SAP Productivity User	0.05 FUE
SAP Developer User	1.0 FUE

The buyer side counter model

SAP runs a default FUE conversion model that maximizes FUE count by assigning Professional User equivalence to ambiguous roles. The buyer side counter model runs the conversion against documented role usage and typically reduces FUE count by 18 to 35 percent.

The discipline is to inventory actual user activity for 90 to 180 days before running the FUE conversion. Users who log in twice per quarter are not Professional Users regardless of their named user license. Documenting actual usage justifies a lower FUE category.

RISE inclusion decision

RISE with SAP is the bundled cloud transition product that packages S/4HANA Cloud, infrastructure, business technology platform, and managed services. Customers can include RISE in the GAP at signing or negotiate it separately at the transition decision point.

When to include RISE in the GAP

• Transition timeline within 24 months. Including RISE captures the GAP discount band.
• S/4HANA Cloud as the target deployment model. Not S/4HANA on premise.
• Multi entity transition. Single GAP simplifies the multi entity rollout.
• Documented business case. Cloud transition approved by the executive committee.

When to defer RISE from the GAP

• Transition timeline beyond 36 months. Preserve leverage for the later decision.
• S/4HANA on premise as the target. RISE not relevant.
• Active hyperscaler partnership. Customer running on AWS, Azure, or GCP independently.
• Multiple SI partners in play. RISE constrains the SI choice.

Ramp commit structure

GAP supports ramp commit structures for customers with predictable growth profiles. Year one spend is lower, scaling to the full commit by year three.

Ramp deal mechanics

1. Year one. 60 to 75 percent of full commit. Reflects deployment ramp.
2. Year two. 85 to 95 percent of full commit.
3. Year three. Full commit. Baseline for renewal.
4. Discount band. Locked at signing across all three years.
5. Catch up mechanism. Consumption above ramp commits to discounted rate.
6. Renewal pricing reference. Year three commit, not market reset.

Renewal posture

GAP renewals follow the broader SAP renewal pattern. The customer that prepares twelve months in advance with documented entity scope, FUE evolution, and indirect access exposure captures the discount band.

Twelve month renewal preparation

1. T minus 12 months. Audit the GAP entity scope. Identify carve out and addition candidates.
2. T minus 9 months. Run the FUE conversion update. New roles, transitioned users, S/4HANA progress.
3. T minus 6 months. Update indirect access discovery. New third party applications, document volume growth.
4. T minus 4 months. Build the renewal forecast. ECC sunset, S/4HANA growth, BTP expansion.
5. T minus 2 months. Receive the SAP renewal proposal. Negotiate against the documented model.
6. Signing. Multi year GAP with entity scope flexibility and FUE conversion lock.

What to do next

The checklist takes the SAP customer from where they are today to a negotiated, properly scoped GAP.

1. Inventory the legal entities and SAP footprint. Decide the entity scope intentionally.
2. Lock the currency conversion mechanism. Fixed, floating, or annual reset.
3. Run the indirect access discovery. Identify third party applications and volumes.
4. Run the FUE conversion counter model. Document role usage. Reduce FUE count.
5. Decide RISE inclusion. Against the transition timeline, not the discount headline.
6. Negotiate the discount band by product line. ECC, S/4HANA, Ariba, SuccessFactors, BTP.
7. Time to SAP Q4. October to December is the discount window.
8. Run the deal through Vendor Shield. Independent buyer side review before signature.

Frequently asked questions

How Redress engages on SAP

Redress runs SAP advisory inside the Vendor Shield subscription, the Renewal Program, the SAP Services practice, and the Software Spend Assessment.

Read the related SAP RISE Negotiation Guide, the SAP Hub, the case studies, the benchmarking service, the management team page, the about us page, and the contact page.