# FinOptory > SAP contract governance, across the full lifecycle, across the entire SAP product portfolio. Two products and one entry offering, all priced on Annual Contract Value (ACV). ## Brand story SAP contracts are negotiated carefully and signed under pressure. After signing, customers typically return to operations and projects. The systematic discipline for ongoing steering, deadlines, scope drift, BTP credit consumption, FUE evolution, derived charges, SLA enforcement, renewal preparation, is rarely staffed and almost never tooled. The result is the same across customers: overpayment, missed renewal windows, surprise invoices, and weak negotiation positions twelve to eighteen months later. FinOptory exists to close that gap. Not as a one-off optimization, not as a tool that replaces SAP expertise, but as continuous post-signature governance over the full contract lifecycle and across the entire SAP product portfolio. The phase is the differentiator, not the technology. AI helps us read documents, reconcile data and surface anomalies at speed. People carry accountability, decide on recommendations, and prepare every customer conversation. The customer always decides. FinOptory is operated by Green Dopamine GmbH, Villach, Austria. The team combines SAP Basis, SAP licensing, financial steering and software engineering experience built up over more than fifteen years of enterprise SAP work. --- ## Products ### FinOptory Self-Service: "You steer." The platform you operate yourself. FinOptory AI analyzes your SAP contracts, reconciles them against operational data, and surfaces deviations. Your team evaluates and acts. What it does: - Contract intake: upload signed contracts and amendments. AI parses Order Forms, SLAs, scope and pricing. - Operational sync: connect SAP4Me, BTP Cockpit, Cloud ALM and CPEA reporting via the BTP Integration Suite. - Drift detection: continuous reconciliation of contract scope against actual consumption (BTP credits, FUE, subscriptions, package budgets). - Renewal calendar: visibility on auto-renewal windows, notice periods, options and price caps. - Cost simulation: what-if scenarios for renewal, scope change, growth. What it is not: - A SAP license management tool replacing SAM platforms. - A vendor-neutral procurement marketplace. - A consulting engagement. Pricing: 1.5 percent of the ACV under management, per year. Includes platform, AI analysis, drift detection and renewal calendar. Customer team operates the platform. URL: https://finoptory.ai/en/self-service/ ### FinOptory Managed Service: "We steer. You decide." A dedicated team operates the platform with you. Weekly recommendations, structured renewal preparation, escalation paths into SAP. What is included: - Everything in Self-Service. - A named contract manager and FinOps expert assigned to your portfolio. - Bi-weekly governance reviews with concrete recommendations. - Renewal governance: structured preparation 12 to 18 months before contract end. - Escalation to SAP when issues are identified (derived charges, SLA breaches, scope disputes). - Documentation of decisions and rationale, for executive reporting and audit. What it is not: - A reseller or systems integrator. FinOptory is independent of SAP and SI partners. - A SAP negotiation service that promises specific discount levels. Outcomes depend on the contract and the customer position. Pricing: 2.2 percent of the ACV under management, per year. Add-ons available for portfolios above four product types or with three or more renewals within twelve months. URL: https://finoptory.ai/en/managed-service/ ### Contract Check: clarity in four weeks The entry offering. One contract, four weeks, fixed price. What you get: - Gap report comparing contracted scope to actual consumption. - Rightsizing analysis across the contract building blocks (FUE, subscriptions, BTP credits, package budgets). - Top-5 quick wins, prioritized by effort and impact. - Governance recommendation: whether a one-time clean-up is enough or ongoing steering is justified. - Three-page executive brief for leadership. What it is not: - A full SAP audit. - A negotiation engagement. - A long discovery project. Four weeks, fixed scope, fixed price. Price: EUR 7,900 net, one contract. Customers who continue with Self-Service or Managed Service can credit 50 percent of the Contract Check fee against the first year. URL: https://finoptory.ai/en/contract-check/ --- ## SAP product coverage FinOptory governs contracts across all nine SAP product types found in enterprise portfolios: 1. **On-Premise licensing**: classic perpetual licenses, maintenance and migration paths into RISE. 2. **SAP BTP (Business Technology Platform)**: Integration Suite, Build, HANA Cloud, Kyma, Analytics Cloud and AI services. Credit-based via CPEA or BTPEA. 3. **RISE with SAP**: bundled offering combining S/4HANA Cloud, infrastructure and managed services into a single subscription. 4. **S/4HANA Cloud (Public and Private Edition)**: standalone subscriptions outside RISE. 5. **SuccessFactors**: HCM suite, often contracted separately with its own renewal cycle. 6. **Ariba**: procurement suite, frequently bundled with separate transaction fees. 7. **Concur**: travel and expense, typically per-user pricing. 8. **IBP (Integrated Business Planning)**: planning suite, often per-user with module variations. 9. **Signavio**: process intelligence, increasingly bundled with RISE. Each product type has its own contract structure, pricing logic, scope definitions and renewal mechanics. Governance has to account for all of them, including how they interact (for example RISE pulling in BTP credits, or SuccessFactors renewing independently of the core S/4HANA contract). --- ## Target audience SAP customers with complex portfolios, globally. Typical signals: - Annual SAP spend above EUR / USD 2 million. - Two or more SAP product types in operation. - Upcoming renewal in the next 12 to 24 months, or a recent RISE migration. - Internal accountability for SAP spend sits across IT leadership, vendor management, procurement and finance, without a single owner. Typical roles engaging with FinOptory: CIO, IT director, head of SAP, vendor management lead, procurement category manager for software, FinOps lead. FinOptory operates from Austria but serves customers globally. Engagements are in English or German. --- ## Methodology and philosophy **Post-signature, not pre-signature.** Negotiation support is a one-time event. Governance is the rest of the contract lifetime. FinOptory is built for the second part. **AI as a tool, not a differentiator.** AI is the tool, not the brand. FinOptory leads with the phase it operates in: post-signature governance. AI helps read documents, reconcile data and detect deviations at scale. It does not replace judgment. **Humans carry accountability.** Every recommendation is reviewed by a named SAP contract expert before it reaches the customer. The customer always decides. **Independence.** FinOptory is independent of SAP, resellers and systems integrators. The only contractual relationship is with the customer. **No fear marketing.** Complexity is the topic, not the customer. SAP contracts are intricate by design. The goal is to deploy investment deliberately, not to "cut costs". Cost reduction is sometimes the outcome, never the starting frame. **Fixed prices.** Self-Service, Managed Service and Contract Check are all priced transparently. No day rates, no T&M, no hidden change orders. --- ## Resources - **Glossary**: definitions of key SAP contract terms (ACV, FUE, CPEA, BTPEA, derived charges, Order Form, SLA, PCE, renewal governance and more). https://finoptory.ai/en/resources/glossary/ - **Contract Anatomy**: a structured walk-through of the building blocks of a SAP RISE contract, with links to public SAP reference documents. https://finoptory.ai/en/resources/contract-anatomy/ - **Blog**: practical insights from project work on BTP credits, ACV structure, SLA enforcement, renewal preparation and FinOps for SAP. https://finoptory.ai/en/resources/blog/ --- ## FAQ **What exactly does FinOptory do?** FinOptory is a SAP contract governance offering with two product tiers: Self-Service (the platform you operate) and Managed Service (a dedicated team operates the platform with you). Both run continuously across the contract lifecycle. **How is FinOptory different from SAP license management tools?** Classic SAM tools focus on license compliance and user counting. FinOptory addresses commercial contract steering: ACV tracking, phase management, derived charges, funding allocation, renewal preparation, cost simulation. FinOptory complements SAM, it does not replace it. **What is the entry point?** Contract Check: one contract, four weeks, EUR 7,900 net. The output is a gap report, rightsizing analysis, top-5 quick wins and a governance recommendation. 50 percent is creditable against a follow-on Self-Service or Managed Service engagement. **How is pricing structured?** ACV-based. Self-Service is 1.5 percent of the ACV under management per year. Managed Service is 2.2 percent. Contract Check is a fixed EUR 7,900 for one contract. **Are contract data secure?** EU hosting, GDPR compliant, SOC 2 infrastructure. The customer owns the data. On contract end, full export within four weeks. No lock-in. **Can FinOptory negotiate with SAP on our behalf?** FinOptory prepares the negotiation, builds the position, supports escalation. The customer remains the contractual counterparty to SAP. FinOptory is not a reseller. --- ## Pillar knowledge resources Eight pillars cover the full post-signature governance surface. Each pillar contains a long-form hub (~7,000 words), six clusters and three deep-dive supporting posts. Together they map every governance moment from contract intake through renewal across all SAP product types. ### Pillar 1: SAP Contract Governance (foundational) What it covers: the four governance moments (usage, authorizations, infrastructure, cost), the four roles (Contract Manager, Procurement, Controlling, Executive), the nine SAP product types, the maturity model from ad-hoc to continuous governance, self-service vs managed service decision framework, post-signature operating rhythm. Hub: https://finoptory.ai/en/resources/sap-contract-governance/ ### Pillar 2: SAP Business AI What it covers: SAP Business AI 2026 overview (Joule, AI Units, agents, foundation models), three consumption pools, per-user-per-month with monthly expiration mechanics, Joule skills and agents architecture, Business AI inside RISE contracts, EU AI Act requirements for SAP customers, AI Units monthly burndown, EU AI Act documentation obligations, Premium Plus discontinuation impact. Hub: https://finoptory.ai/en/resources/sap-business-ai/ ### Pillar 3: CPEA/BTPEA Credits and BTP FinOps What it covers: CPEA vs BTPEA fundamental differences, capacity units depreciation mechanics, credit expiration and overage rules, BTP monitoring across three system stacks, FinOps framework for SAP BTP (Inform, Optimize, Operate), internal cost allocation and chargeback, year-end credit burndown checklist, CPEA-BTPEA renewal strategy, subaccount allocation architecture. Hub: https://finoptory.ai/en/resources/cpea-btpea-credits-fully-understood/ ### Pillar 4: Digital Access What it covers: Digital Access and DAAP terminology, the nine document types, Digital Access in RISE contracts, third-party systems as trigger, audit preparation, integration register method, third-party vendor checklist, RISE Enterprise Agreement scope handling, audit checklist for Digital Access. Hub: https://finoptory.ai/en/resources/digital-access-pillar/ ### Pillar 5: SAP Renewal Strategy What it covers: the 18-month renewal timeline, building the data foundation, critical renewal clauses, renewal stakeholder architecture, CPI clauses in renewal pricing, self-reporting overage rules, auto-renewal notice deadlines, BTP renewal negotiation input, exit rights in SAP contracts. Hub: https://finoptory.ai/en/resources/sap-renewal-strategy/ ### Pillar 6: SAP License Efficiency What it covers: Named User vs FUE licensing, authorizations and FUE classification cost mechanics, USMM/LAW/SAM4U toolset, ongoing audit preparation, portfolio license governance, license maturity model, FUE authorization levers, test user classification rules, SAP audit survival guide. Hub: https://finoptory.ai/en/resources/lizenz-effizienz-pillar/ ### Pillar 7: BS7 Roadmap and SAP Transition What it covers: BS7 maintenance end 2027 decision matrix, extended maintenance options 2027-2030, transition option mechanics and RISE credit, on-premise license credit at RISE migration, dual-use period between ECC and S/4HANA, shelfware cleanup at RISE transition, BS7 2027 checklist, transition option application howto, hybrid operations between ECC and S/4HANA. Hub: https://finoptory.ai/en/resources/bs7-roadmap-pillar/ ### Pillar 8: SAP Vendor Management What it covers: SAP account management roles and incentives, escalation step-by-step, vendor lock-in mitigation, cross-functional SAP governance, M&A and carve-out license handling, building internal SAP contract knowledge, escalation 5-step howto, affiliate licensing in groups, SAP account management incentive mechanics. Hub: https://finoptory.ai/en/resources/sap-vendor-managen/ --- ## Wissensdatenbank: Cluster und Deep-Dives Individual cluster articles and deep-dive supporting posts for all eight pillars. Each entry summarizes the core argument of the article. Entries are grouped by pillar and sorted alphabetically by title within each group. ### Pillar 1: SAP Contract Governance #### Four Roles, One SAP Contract Governance Model SAP contract governance requires four distinct roles to function: Contract Manager, Procurement, Controlling, and Executive. Each role operates on a different time horizon and holds different information. When one role is absent, governance gaps form that compound over the contract term. The article describes how the four roles interact and what breaks down when they work in isolation. URL: https://finoptory.ai/en/resources/blog/four-roles-sap-contract-governance/ #### Governance Moments in SAP Contracts: When You Need to Step In A governance moment is a specific point in the contract lifecycle where a decision is both possible and consequential. Missing it means accepting a default outcome. The article maps the most common governance moments across RISE, BTP, SuccessFactors, and on-premise contracts, explaining which ones open and close and what acting on them enables. URL: https://finoptory.ai/en/resources/blog/governance-moments-sap-contracts/ #### Internal Chargeback for SAP Costs: Where SAP-Native Tools Reach Their Limits Allocating SAP cloud contract costs to business units on a causation basis is a governance task that SAP-native tooling does not fully solve. Classical SAM platforms measure license compliance; they do not distribute consumption costs. The article examines which data sources exist, where they fall short, and what a practical chargeback model for RISE and BTP looks like. URL: https://finoptory.ai/en/resources/blog/sap-cost-internal-chargeback/ #### Post-Signature SAP Contract Governance: Why the Phase Matters The distinction between pre-signature and post-signature governance is not semantic. Negotiation ends at signing; governance begins there and runs for the full contract term. The article defines what post-signature governance covers, which governance moments it includes, and why most governance problems originate not in weak negotiation but in the absence of an operating rhythm after the contract is signed. URL: https://finoptory.ai/en/resources/blog/post-signature-sap-contract-governance/ #### SAP Contract Governance Across All 9 SAP Product Types: An Overview Enterprise SAP portfolios span multiple product types with different contract structures, billing cycles, and compliance requirements. A defensible governance model must address all nine. The article maps each product type, the governance moments it produces, and how product interactions, such as RISE pulling in BTP credits, create cross-contract dependencies. URL: https://finoptory.ai/en/resources/blog/sap-contract-governance-nine-product-types/ #### SAP Contract Governance Maturity Model: Where Does Your Organization Stand? Four maturity levels describe the range from reactive license compliance to continuous, strategically anchored governance. A ten-question self-assessment helps organizations identify their current level. The article explains what distinguishes each level and which investments move an organization from one to the next. URL: https://finoptory.ai/en/resources/blog/sap-contract-governance-maturity-model/ #### SAP RISE Auto-Renewal: The 12-Month Trap RISE contracts renew automatically unless terminated within a specified notice window, typically twelve months before contract end. Most contract structures carry this clause without making it prominent. The article explains when the window applies, how it is anchored in the Enterprise Agreement, and how to set up governance that ensures the decision is made actively rather than by default. URL: https://finoptory.ai/en/resources/blog/sap-rise-auto-renewal-trap/ #### Self-Service or Managed Service for SAP Contracts: A Decision Guide Both FinOptory product paths govern the same contract landscape. The choice depends on internal capacity, the pace at which governance depth should be built, and the complexity of the portfolio. The article works through the criteria that distinguish organizations for whom a self-operated platform is appropriate from those where a managed team delivers more value. URL: https://finoptory.ai/en/resources/blog/self-service-or-managed-service-decision-guide/ #### Why BTP Credits Often Expire at Year-End and What You Can Do About It Credit expiration in BTP is a structural feature of commit-to-consume contracts, not an edge case. The article identifies the most common constellations that produce expiration, explains what drives them technically, and describes what structured monitoring from the start of the contract year enables compared to reactive checks in Q4. URL: https://finoptory.ai/en/resources/blog/btp-credits-year-end-expiration/ ### Pillar 2: SAP Business AI #### Business AI in the RISE Contract: What Is Included, What Is Add-On, and Where the Aggregation Trap Waits RISE contracts include some Business AI components by default and require separate add-ons for others. The article identifies which components are bundled in the standard tier, which require a separate Order Form, and where organizations incorrectly aggregate AI Unit consumption across the three independent consumption pools. URL: https://finoptory.ai/en/resources/blog/sap-business-ai-in-rise-contract/ #### EU AI Act and SAP Business AI: What Changes from August 2026 and What You Must Document Yourself From August 2026 the EU AI Act applies fully to high-risk AI systems. SAP provides certifications at the platform level, but documentation, risk assessments, and human oversight requirements remain with the customer. The article maps which SAP Business AI use cases fall in scope and what documentation the regulation requires from deploying organizations. URL: https://finoptory.ai/en/resources/blog/eu-ai-act-sap-business-ai/ #### EU AI Act from August 2026: What SAP Business AI Users Must Document Compliance under the EU AI Act is not complete when SAP certifications are in place. Customer-side documentation obligations cover risk management, data governance, transparency, and human oversight. The article provides a structured overview of what must be documented, by whom, and by which deadline. URL: https://finoptory.ai/en/resources/blog/eu-ai-act-sap-documentation-requirements/ #### Joule, Skills, Agents, and Foundation Models: What Distinguishes SAP's AI Family Commercially SAP Business AI is not a single product. It encompasses Joule for Users, Skills, Agents, and Foundation Models, each with its own licensing logic and consumption model. The article distinguishes these components commercially, explains how Skills differ from Agents, and identifies which Foundation Models are accessible and at what cost. URL: https://finoptory.ai/en/resources/blog/joule-skills-agents-foundation-models/ #### Premium Plus Has Been Deprecated Since June 2025: What Changed for SAP RISE Customers Premium Plus was discontinued in June 2025, changing how Business AI features are bundled and priced within RISE contracts. Customers who held Premium Plus contracts need to understand what was removed, what continues in the new packaging, and which governance moments arise at their next renewal. URL: https://finoptory.ai/en/resources/blog/sap-premium-plus-deprecation-2025/ #### PUPM in SAP Business AI: How the Per-User-per-Month Model Really Works PUPM packages in SAP Business AI allocate a fixed quota of AI requests per user per month. Unused requests expire at month-end, not at year-end. The article explains the assignment mechanics, how package scoping by solution area prevents cross-product pooling, and what this means for planning, budget forecasting, and user turnover. URL: https://finoptory.ai/en/resources/blog/pupm-sap-business-ai/ #### Three Consumption Pools in SAP Business AI: What Separates AI Units, Capacity Units, and BDC Credits SAP Business AI bills through three separate pools that cannot be aggregated or offset against each other: AI Units for generative AI, Capacity Units for classical AI services, and BDC Credits for Business Data Cloud. The article explains each pool's mechanics, expiration rules, and what the separation means for budgeting and governance. URL: https://finoptory.ai/en/resources/blog/sap-business-ai-three-consumption-pools/ #### What Happens to Unused AI Units at Month-End? AI Unit packages under the PUPM model expire at the end of each calendar month, creating a different governance cadence than annual credit models. The article explains the two expiration logics in SAP Business AI, how pooling within a solution area affects the outcome, and which monthly review steps prevent recurring waste. URL: https://finoptory.ai/en/resources/blog/ai-units-monthly-expiration/ #### What SAP Business AI Really Is in 2026: Three Layers, Joule Studio 2.0, and the End of Premium Plus SAP Business AI in 2026 consists of three architectural layers (Context, Build, Governance), a shared frontend in Joule, and embedded AI functions across more than 35 SAP solutions. Packaging has changed materially since 2025. The article explains the current architecture, what has changed, and where governance moments arise as a result. URL: https://finoptory.ai/en/resources/blog/sap-business-ai-2026-overview/ ### Pillar 3: CPEA/BTPEA Credits #### BTP Credit Expiration and Overage: What Happens to Unused Credits at Year-End Unused BTP credits expire at the end of the contract period. Once the credit pool is exhausted, overage is billed at full list price without volume discounts. The article explains both rules, the structural mechanics behind them, and how governance prevents both expiration loss and overage costs. URL: https://finoptory.ai/en/resources/blog/credit-expiration-overage-rules/ #### BTP Monitoring Strategy: The Data Points You Need to Track Continuously The BTP Cockpit provides balance statements and live entitlement views, but neither produces a governed consumption picture on its own. The article identifies the data points required for continuous monitoring, explains how to set meaningful alert thresholds, and describes what connects subaccount-level data to internal cost allocation. URL: https://finoptory.ai/en/resources/blog/btp-monitoring-three-system-stack/ #### BTP Year-End Credit Expiry: When You Must Review Your Burndown at the Latest Preventing BTP credit expiration requires acting well before year-end, not at it. The article provides an operational timeline: which review steps belong in which month, what a burndown curve reveals that monthly balance statements do not, and how to govern toward full consumption without triggering overage. URL: https://finoptory.ai/en/resources/blog/year-end-credit-burndown-checklist/ #### Capacity Units and Depreciation Groups: How BTP Consumption Is Actually Measured BTP is billed in credits but measured in Capacity Units, a service-specific technical layer that most governance processes never reach. Understanding CUs and depreciation groups is the prerequisite for setting meaningful alert thresholds and building reliable consumption forecasts. The article explains the mechanics of both concepts and makes them directly actionable. URL: https://finoptory.ai/en/resources/blog/capacity-units-depreciation-mechanics/ #### CPEA or BTPEA at Your Next Renewal: What the Migration Actually Means BTPEA is SAP's strategic successor to CPEA for BTP contracts, but migration is not automatically the right move at every renewal. The article identifies the concrete criteria that determine whether transitioning makes sense, explains the differences in service catalog scope and deprecation policy, and describes what the governance implications of each path are. URL: https://finoptory.ai/en/resources/blog/cpea-btpea-renewal-strategy/ #### CPEA vs. BTPEA: What You Need to Know About the Two Credit Models CPEA and BTPEA share the same core structure: upfront credit purchase with flexible consumption. They diverge in service catalog scope and long-term availability. The article explains the practical difference between the two models and what it means for organizations deciding which contract vehicle to use for the next BTP term. URL: https://finoptory.ai/en/resources/blog/cpea-vs-btpea-the-real-difference/ #### FinOps Inform, Optimize, Operate: Applying the Framework to SAP BTP The FinOps Foundation framework explicitly includes Licensing as a scope since 2024. SAP BTP, with its expiring credits, overage rules, and subaccount-level consumption data, fits the framework well. The article maps all three FinOps phases to BTP governance and explains which capabilities are required in each phase. URL: https://finoptory.ai/en/resources/blog/finops-framework-for-sap-btp/ #### Internal Cost Allocation for BTP: Chargeback Models for Hybrid Portfolios Without the right subaccount structure, cause-based cost allocation for BTP is technically impossible. The article describes the organizational and technical prerequisites for reliable chargeback, explains how BTP Balance Statements provide the only structured data source available, and identifies where SAP-native tooling reaches its limits. URL: https://finoptory.ai/en/resources/blog/internal-cost-allocation-cpea-btpea/ #### Subaccount Cost Allocation: Assigning BTP Costs to Cost Centers on a Cause-Based Basis Cost allocation for BTP requires that the Global Account subaccount structure was designed with allocation in mind. Whatever is not separated at the subaccount level cannot be separated in reporting later. The article walks through how to build a cause-based allocation model step by step and identifies the governance moments where architecture decisions and reporting requirements converge. URL: https://finoptory.ai/en/resources/blog/subaccount-allocation-architecture/ ### Pillar 4: Digital Access #### SAP Digital Access and Indirect Access: Terms and History Explained Indirect Access and Digital Access describe the same underlying issue from different eras of SAP licensing policy. Understanding the distinction clarifies why many existing customer contracts still have open questions in 2026 and what the term DAAP means in practical governance. The article traces the history from the pre-2018 Indirect Access model to the document-based Digital Access framework. URL: https://finoptory.ai/en/resources/blog/digital-access-glossary-daap/ #### SAP Digital Access Audit Checklist: 10 Steps to Confident Audit Preparation Digital Access is one of the most frequent findings in SAP Enhanced Audits. The article provides ten preparation steps that organizations should complete before the audit window opens: from documenting the integration inventory to clarifying DAAP status and establishing document volume tracking at the system level. URL: https://finoptory.ai/en/resources/blog/digital-access-audit-checklist/ #### SAP Digital Access in an Audit: What SAP Examines and How to Be Prepared In an Enhanced Audit, SAP systematically reviews the integration architecture and reconstructs which technical users generated which document types. The article explains how the Global License Auditing team approaches this review, which findings surface most often, and how an organization's negotiating position changes depending on whether the integration inventory was documented in advance. URL: https://finoptory.ai/en/resources/blog/digital-access-audit-preparation/ #### SAP Digital Access: The Nine Document Types and How Licensing Works Digital Access creates a licensing obligation when a third-party system writes one of nine defined document types into SAP via an SAP interface. Reading data without writing does not trigger a license. The article explains each of the nine document types, the difference between the old Indirect Access model and the current document-based model, and what the Static Read exception covers. URL: https://finoptory.ai/en/resources/blog/nine-document-types-digital-access/ #### Digital Access in RISE Contracts: What the Enterprise Agreement Inclusion Covers and What It Doesn't Many RISE customers assume Digital Access is fully included in their Enterprise Agreement. For internal integrations, that is often correct. External systems, IoT platforms, and partner portals typically fall outside the scope of that inclusion. The article explains what "internal" means contractually and which integration categories require separate DAAP licensing. URL: https://finoptory.ai/en/resources/blog/digital-access-in-rise-contracts/ #### RISE Enterprise Agreement and Digital Access: What the Scope Actually Covers RISE Enterprise Agreements frequently include unlimited Digital Access for internal integrations, but the boundary of "internal" is defined in the contract, not by common usage. The article maps where the unlimited inclusion ends, identifies the integration patterns that fall outside it, and explains which governance moments arise when the integration footprint expands. URL: https://finoptory.ai/en/resources/blog/rise-enterprise-agreement-scope/ #### The Integration Register as the Compliance Foundation for Digital Access The central question for Digital Access governance is: which systems have an interface to SAP, and what do they write into it? The integration register is the governance tool that answers this question continuously. The article explains how to build and maintain it, what it must document, and why a one-time audit document is not sufficient. URL: https://finoptory.ai/en/resources/blog/integration-register-method/ #### Third-Party Vendor Checklist for Digital Access: Which Systems to Review for License Relevance Today The integration landscape typically grows faster than license status is updated. Before a RISE migration or an Enhanced Audit, a systematic review of third-party systems is the prerequisite for a defensible Digital Access position. The checklist categorizes system types by license relevance and identifies where clarification is needed. URL: https://finoptory.ai/en/resources/blog/third-party-vendor-checklist/ #### Which Third-Party Systems Trigger SAP Digital Access: CRM, WMS, MES, RPA, E-Commerce Whether a third-party system creates a Digital Access obligation depends not on the system category but on whether it creates one of the nine defined document types in SAP. The article categorizes the most common integration patterns, identifies which document types each system type typically triggers, and explains how to assess the governance position for each one. URL: https://finoptory.ai/en/resources/blog/third-party-systems-digital-access/ ### Pillar 5: SAP Renewal Strategy #### Auto-Renewal Deadlines in SAP Contracts: Which Notice Windows Apply and When SAP contracts renew automatically when notice deadlines pass unobserved. Different products carry different notice windows, and managing them by product silo creates a blind spot when multiple renewals converge. The article covers which deadlines apply to RISE, BTP, SuccessFactors, and Ariba, and describes a structured approach to governing them across the full portfolio. URL: https://finoptory.ai/en/resources/blog/auto-renewal-notice-deadlines/ #### BTP Consumption Data as Negotiation Input for SAP Renewal BTP credit data documents actual platform utilization at a granularity level not captured by FUE metering. Yet it is rarely prepared as structured negotiation input before renewal. The article explains how to build a time series from balance statements and use consumption trends to justify the credit volume in the next contract term. URL: https://finoptory.ai/en/resources/blog/btp-renewal-negotiation-input/ #### Building the Data Foundation for SAP Renewal Negotiations Renewal negotiations are decided by data, not by negotiation technique. The article describes the four data categories that constitute a solid renewal position, explains what is commonly absent in practice, and outlines what preparation looks like across the twelve months before the renewal window opens. URL: https://finoptory.ai/en/resources/blog/renewal-data-foundation-checklist/ #### CPI Clauses in SAP Contracts: How Automatic Price Adjustments Work and How to Cap Them CPI clauses determine how and within what limits SAP may adjust prices at renewal. The mechanism is documented in Schedule 5 of the RISE Enterprise Agreement, but contract-specific overlays can modify the standard rules. The article explains the full layered structure of CPI provisions and which clauses to negotiate during renewal preparation. URL: https://finoptory.ai/en/resources/blog/cpi-clauses-renewal-pricing/ #### Critical Clauses in SAP Contracts: What Is Negotiable at Renewal Not every contract clause has equal governance weight. Some determine pricing flexibility for the entire next term; others govern what happens when organizational structure changes. The article identifies six clause areas that should be reviewed in every renewal preparation cycle and explains what outcomes are achievable when they are addressed proactively. URL: https://finoptory.ai/en/resources/blog/critical-renewal-clauses/ #### Negotiating Exit Rights in SAP Contracts: Data Portability, Termination Assistance, Transition Periods Exit clauses define what happens when a contract ends: data return procedures, transition assistance periods, cost responsibilities, and conditions for early termination. The standard RISE Enterprise Agreement covers some of these areas and leaves others open. The article explains which exit provisions to address at renewal and what substantive outcomes are achievable. URL: https://finoptory.ai/en/resources/blog/exit-rights-sap-contracts/ #### SAP Renewal Stakeholders: Who Needs to Be Involved, Internally and Externally Renewal requires four roles to operate in parallel: Contract Manager for documentation and deadlines, Procurement for mandate and negotiation, Controlling for numbers and allocation, and Executive for decision authority. Assembling the team only in the final weeks before expiry forfeits the leverage that early preparation builds. The article describes the full stakeholder architecture and the timing each role requires. URL: https://finoptory.ai/en/resources/blog/renewal-stakeholder-architecture/ #### Self-Reporting and Overage in SAP Contracts: What Customers Must Report Every Month The RISE Enterprise Agreement places the obligation to report excess consumption on the customer, not on SAP. No automatic notification system substitutes for active monitoring. The article explains what must be reported, when, and how unmanaged overage creates open items precisely when the renewal conversation begins. URL: https://finoptory.ai/en/resources/blog/self-reporting-overage-renewals/ #### The SAP Renewal Timeline: Preparation Starts 12 to 18 Months Before Contract Expiry SAP initiates renewal dialogue 12 to 18 months before contract expiry, operating with structured sales processes and a complete consumption history. Organizations that begin preparation in the same window negotiate as equals. Those that start later negotiate under time pressure. The article maps the full preparation timeline and identifies the most common mistakes that forfeit the renewal governance moment. URL: https://finoptory.ai/en/resources/blog/sap-renewal-timeline-18-months/ ### Pillar 6: SAP License Efficiency #### Authorizations and FUE Costs: How Role Design Determines Your License Base In S/4HANA Cloud, the assigned authorization determines a user's FUE type, not actual system usage. Assigning a role with Advanced authorization counts the user as Advanced, even if the corresponding transaction is never executed. This means role design is a license cost decision, not only a security decision. The article explains the classification mechanics and their direct impact on the FUE base. URL: https://finoptory.ai/en/resources/blog/authorizations-fue-classification/ #### Classifying Test Users in SAP Correctly: What Counts as License-Relevant and What Does Not Test users are among the most common findings in SAP Enhanced Audits. The classification rule depends on the contractual basis: production systems are always license-relevant, non-production systems depend on what the contract specifies. The article clarifies which system types qualify as test environments under SAP contract language and how to document the classification defensibly. URL: https://finoptory.ai/en/resources/blog/test-user-classification-sap/ #### FUE Levers Through Authorization Roles: How Role Design Directly Affects License Costs When a user is assigned a role with Advanced authorization in S/4HANA, that user counts as Advanced regardless of actual transaction use. Role design is therefore a direct lever on the FUE base and on license costs. The article explains how the authorization-based classification model works and how optimization through role redesign translates to measurable cost reduction. URL: https://finoptory.ai/en/resources/blog/fue-authorization-levers/ #### License Governance Across Multiple SAP Product Types: A Portfolio Perspective for Hybrid Landscapes Organizations running RISE, BTP, SuccessFactors, and Ariba in parallel manage four different licensing models with different metrics, billing cycles, and compliance requirements. No single governance process covers all of them. The article maps the full portfolio of SAP product type licensing models and describes what a cross-type governance structure needs to account for. URL: https://finoptory.ai/en/resources/blog/portfolio-license-governance/ #### Named User and FUE: Understanding the Two Worlds of SAP Licensing On-premise SAP systems use the named user principle: every individual with access requires an assigned license. Cloud systems under RISE and GROW use Full Use Equivalents: customers buy a pool of FUEs and draw from it. The article explains both models, the key differences in how compliance is measured, and what the shift from named user to FUE means for ongoing governance. URL: https://finoptory.ai/en/resources/blog/named-user-vs-fue-licensing/ #### SAP Audit Preparation: Ongoing Measures Instead of Emergency Response Organizations that run quarterly self-audits, clean up inactive accounts systematically, and address classification gaps before an Enhanced Audit enters the conversation from a position of strength. The article describes which ongoing measures constitute structured audit readiness and how the difference between proactive and reactive preparation affects the audit outcome. URL: https://finoptory.ai/en/resources/blog/sap-audit-preparation-license/ #### SAP Audit Survival Guide: What to Do When an Audit Is Already Underway When SAP announces a license measurement, the response in the first days determines how controlled the subsequent process will be. The article walks through the four phases of a structured audit response, explains what data needs to be submitted at each phase, and identifies the most common process mistakes that worsen the outcome. URL: https://finoptory.ai/en/resources/blog/sap-audit-survival-guide/ #### SAP License Maturity Model: Four Levels with a Self-Assessment SAP license management maturity ranges from reactive classification on demand to strategically embedded continuous governance. A four-level model with an eight-question self-assessment helps organizations identify their starting point. The article explains what distinguishes each level and which specific investments move organizations up the maturity curve. URL: https://finoptory.ai/en/resources/blog/license-maturity-model/ #### USMM, LAW, and SAM4U: Understanding the SAP License Measurement Toolkit SAP provides three standard tools for license measurement, each with a distinct purpose: USMM for user measurement, LAW for system landscape reporting, and SAM4U for ongoing visibility. Running them only when an audit is announced misses the governance value they provide in the regular operating rhythm. The article explains how the three tools work together and what each one can and cannot do. URL: https://finoptory.ai/en/resources/blog/usmm-law-sam4u-tools/ ### Pillar 7: BS7 Roadmap #### BS7 Checklist 2027: Ten Steps to Your Migration Decision Mainstream Maintenance for SAP ERP 6.0 EhP 6-8 ends on December 31, 2027. Organizations that reach that date without a decision have made one by default: Extended Maintenance at a higher rate. The checklist provides ten steps a Director SAP Platform needs to work through to reach a data-based decision before time pressure dictates the outcome. URL: https://finoptory.ai/en/resources/blog/bs7-2027-checklist-decision-path/ #### BS7 End of Maintenance 2027: Three Scenarios and Their Decision Matrix Three paths exist for organizations running SAP ERP 6.0 EhP 6-8 past 2027: Extended Maintenance, RISE migration, or the Transition Option. Each has distinct contract mechanics, cost implications, and lead time requirements. The article maps all three scenarios, describes the data needed to evaluate each, and identifies which decision timeline applies. URL: https://finoptory.ai/en/resources/blog/bs7-decision-matrix-rise-keep-leave/ #### Calculating Extended Maintenance: Understanding the +2% Rule and Base Reduction Extended Maintenance adds two percentage points to the maintenance base. Whether that is manageable depends entirely on what is in the base. The article explains how the maintenance base is calculated, which line items can be removed before the cutover date, and what the numerical difference looks like across different base compositions. URL: https://finoptory.ai/en/resources/blog/extended-maintenance-options-2027-2030/ #### Dual-Use Period: Governance During Parallel ECC and RISE Operations During a RISE migration, on-premise and cloud systems run in parallel for months, sometimes more than a year. Both environments are live, users operate in both, and transactions are posted on both sides. The article explains how the dual-use period creates specific governance challenges around licensing, maintenance billing, and the contractual boundary between systems. URL: https://finoptory.ai/en/resources/blog/dual-use-period-ecc-s4-rise/ #### Hybrid Operations: On-Premise and Cloud Running in Parallel for Years Permanent hybrid operations, where on-premise and RISE environments coexist as an ongoing operating model, are contractually viable but require active governance in four areas: usage rights, SLA boundaries, billing, and license credits. The article explains what makes hybrid operations different from a transitional dual-use period and what each governance area must address. URL: https://finoptory.ai/en/resources/blog/hybrid-operations-ecc-s4-coexistence/ #### On-Premise License Credits for RISE: Credit Types and Mechanics Organizations transitioning from on-premise to RISE can apply existing maintenance investments as credits against the new contract through the Cloud Extension Program. Three credit types exist with different application scopes and conditions. The article explains how each credit type works, how credits are applied against Annual Contract Value, and why the timing of enrollment affects the negotiable amount. URL: https://finoptory.ai/en/resources/blog/license-credit-rise-migration/ #### SAP Shelfware Cleanup: Reduce Maintenance and Build Negotiating Leverage Unused licenses accumulate over years in mature SAP landscapes. A RISE migration opens a time-limited window to put shelfware to strategic use: as an argument in negotiations, as a lever to reduce the maintenance base, and as a foundation for credit calculation. The article explains how shelfware builds up and how systematic cleanup before the migration changes the negotiating position. URL: https://finoptory.ai/en/resources/blog/shelfware-cleanup-rise-transition/ #### SAP Transition Option Application: The Process and Documents You Need The Transition Option subscription window opens between 2028 and 2030 for organizations running EHP7 or EHP8. The application process has specific technical and contractual prerequisites that must be confirmed before SAP processes the order. The article documents what eligibility requires, how the process unfolds, and what to expect between the decision to proceed and a signed contract. URL: https://finoptory.ai/en/resources/blog/transition-option-application-howto/ #### SAP Transition Option: Mechanics, Deadlines, and What the 20% Surcharge Really Means The Transition Option extends on-premise operations through end of 2033 but adds a 20% surcharge to the maintenance base and requires a mandatory Max Success Plan. The article explains the financial mechanics behind the surcharge, the EHP prerequisites that determine eligibility, and how to assess whether the time extension justifies the additional cost. URL: https://finoptory.ai/en/resources/blog/transition-option-rise-credit/ ### Pillar 8: SAP Vendor Management #### Behind the Scenes of SAP Account Management: How AE Quotas and CSM Incentives Shape Your Contract Conversations SAP Account Executives and Customer Success Managers operate with different incentive structures that directly influence what gets discussed and when. AE quotas center on new revenue and expansion; CSM incentives focus on adoption and contract health. Understanding these dynamics helps organizations interpret SAP's commercial outreach and time their own governance conversations accordingly. URL: https://finoptory.ai/en/resources/blog/sap-account-management-incentives/ #### Building and Preserving Internal Knowledge: Embedding SAP Contract Expertise in Your Organization SAP contract expertise is built through experience and erodes through staff turnover. When the person who managed the last renewal leaves, the institutional knowledge often leaves with them. The article describes how contract knowledge can be systematically documented, handed over, and preserved so that governance capability accumulates independent of individual staff. URL: https://finoptory.ai/en/resources/blog/sap-knowledge-building-team/ #### Cross-Functional SAP Governance: How IT, Procurement, and Finance Coordinate SAP contract governance requires information that sits in IT, Procurement, Finance, and Executive simultaneously. When these functions work without a shared process, information gaps emerge and governance moments go unused. The article describes how the four functions interact, where coordination breaks down in practice, and what a workable cross-functional governance model looks like. URL: https://finoptory.ai/en/resources/blog/cross-functional-sap-governance/ #### How to Escalate with SAP: From Service Ticket to Executive Escalation SAP has formal escalation paths that exist outside standard support channels. Organizations that use them deliberately and document each step consistently reach resolutions faster and build a governance record that carries weight in future contract conversations. The article walks through SAP's five-level escalation path and the prerequisites for each step. URL: https://finoptory.ai/en/resources/blog/sap-escalation-step-by-step/ #### M&A, Carve-Outs, and Contract Transfers: SAP Agreements in Corporate Transactions Acquisitions and carve-outs raise immediate questions for SAP contract relationships: who takes over the agreement, what compliance obligations transfer, and when does SAP need to be formally notified. SAP contracts are not automatically transferable. The article explains the contractual basis for change-of-party scenarios and identifies which governance moments M&A events create. URL: https://finoptory.ai/en/resources/blog/m-a-carve-out-sap-licensing/ #### SAP Affiliate Licensing: Covering Group Companies Under Existing SAP Contracts Affiliate licensing clauses define which entities within a corporate group are authorized under an existing SAP contract. The definitions vary by contract version and often go unreviewed until an acquisition, carve-out, or reorganization forces the question. The article explains what affiliate provisions typically cover, what they leave open, and when the topic surfaces as a governance moment. URL: https://finoptory.ai/en/resources/blog/affiliate-licensing-sap-group/ #### SAP Escalation in 5 Steps: A How-To for Service Delivery Problems When SAP service delivery falls short of contractual commitments, formal escalation paths provide a structured alternative to continued standard support tickets. The article outlines five escalation steps from incident ticket to executive escalation, with concrete guidance on documentation requirements and conditions for moving between levels. URL: https://finoptory.ai/en/resources/blog/sap-escalation-5-steps-howto/ #### SAP Vendor Lock-In and Room to Maneuver: Three Dimensions, Four Countermeasures Structural dependency on SAP accumulates across technical, contractual, and organizational dimensions. Organizations that treat this as a one-time problem rather than a continuous governance task lose negotiating leverage over the contract term. The article maps all three dependency dimensions, explains which governance moments they produce, and describes four countermeasures that preserve room to maneuver. URL: https://finoptory.ai/en/resources/blog/vendor-lockin-mitigation-sap/ #### Understanding SAP Account Management: Roles, Incentives, and What That Means for Your Governance SAP's customer-facing roles, including Account Executive, Customer Success Manager, and Technical Account Manager, carry different responsibilities and operate under different incentive structures. Knowing what each role can and cannot decide helps organizations direct conversations to the right counterpart at the right time. The article maps each role and its practical implications for contract governance. URL: https://finoptory.ai/en/resources/blog/sap-account-management-roles/ --- ## Contact - Website: https://finoptory.ai/en/ - Contact form: https://finoptory.ai/en/contact/ - LinkedIn: https://www.linkedin.com/company/finoptory/ Operated by Green Dopamine GmbH, Seehügelweg 1f, 9500 Villach, Austria. VAT ID: ATU78344267.